apparatus and method for processing information in an electric power network

专利摘要:
EVENT PROCESSING SYSTEM FOR AN ELECTRICITY SYSTEM. The present invention relates to a method and apparatus that comprises an agent (400). The agent (400) is configured to receive information (406) from an electrical power network (202). The agent (400) is further configured to identify an event (408) from the information (406). The agent (400) is additionally configured to classify the event (408). The agent (400) is additionally configured to determine whether to initiate an action based on an event classification (408). Agent (400) is additionally configured to initiate action in response to a determination to initiate action
公开号:BR102013008143B1
申请号:R102013008143-4
申请日:2013-04-04
公开日:2020-10-20
发明作者:Vyacheslav Khozikov；Ronald Ward Sackman；George Michael Roe
申请人:The Boeing Company；
IPC主号:

专利说明:

Background of the Invention
[0001] The present description generally refers to electrical energy and, in particular, electrical energy systems. Even more particularly, the present description refers to a method and apparatus for classifying events in an electrical energy system using information collected by agents distributed throughout the electrical energy system.
[0002] An electrical energy source provides electrical energy for loads. The source of electrical energy can generate mechanical, chemical, thermal and / or other types of energy. The source of electrical energy transmits this electrical energy as electrical power to the loads. A source of electrical energy can also store electrical energy that was previously generated. Electricity can be distributed from a number of electric power sources to a number of charges using an electric power grid. An electrical power network is comprised of a number of electrical power sources, loads, nodes and power lines. A node is located at a connection of two or more power lines.
[0003] A smart grid is an electric power network that gathers, distributes and performs operations in response to information about the electric power network. This information may include, for example, without limitation, information about energy use, energy generation, energy flow, and other types of parameters in the electricity network.
[0004] An intelligent grid is allowed to use different types of capture and measurement devices that monitor different parameters in an electric power network and process information about these parameters. This information can be distributed to the electricity grid using, for example, a communications grid for the electricity grid.
[0005] The power grid can use this information to manage changes in power distribution, power generation, power usage and other parameters for the power grid. In particular, the electricity grid can use the information generated by the different capture and measurement devices to maintain the desired energy distribution within the electricity grid.
[0006] With this type of smart grid, concerns about the physical security and information security of the smart grid may be present. For example, a security concern may consist of a cyber attack on the smart grid. In a cyber attack, an unwanted third party, such as an unauthorized computer system, can take control of one or more portions of the smart grid. In some cases, information can be stolen or manipulated in an unwanted way within the smart grid during a cyber attack.
[0007] In addition, with the configurations currently available for a smart grid, processing the information acquired by different capture and measurement devices across the entire power grid can be more difficult and / or more time-consuming than desired. . For example, processing information that is distributed over a communications network for the power grid to identify events and determine how to respond to these events can be more difficult and / or more time-consuming than desired. Therefore, it may be desirable to have a method and apparatus that takes into account at least some of the problems discussed above, as well as other possible problems. Summary of the Invention
[0008] In an illustrative embodiment, an apparatus comprises an agent. The agent is configured to receive information from an electricity network. The agent is additionally configured to identify an event from the information. The agent is additionally configured to classify the event. The agent is further configured to determine whether to initiate an action based on an event classification. The agent is further configured to initiate the action in response to a determination to initiate the action.
[0009] In another illustrative embodiment, a device comprises a plurality of nodes in an electrical power network, a communications network and a number of agents associated with the plurality of nodes. The plurality of nodes is configured to control the electrical energy transmitted over a number of lines in the electricity network. The communications network is configured to transmit information. A number of agents are configured to send information to each other using the communications network. One agent among the number of agents is configured to receive information from the electricity grid. The agent among the number of agents is additionally configured to identify an event from the information. The agent among the number of agents is additionally configured to classify the event. The agent among the number of agents is additionally configured to determine whether to initiate an action based on an event classification. The agent among the number of agents is additionally configured to initiate action in response to a determination to initiate the action.
[00010] In yet another illustrative modality, a method for processing information on an electric power network is present. Information is received from a number of agents on the electricity grid. An event is identified from the information. The event is classified. A determination is made as to whether to initiate an action based on an event classification. The action is initiated in response to a determination to initiate the action.
[00011] The features and functions can be achieved independently in several modalities of the present description or they can be combined in still other modalities in which the additional details can be observed in reference to the following description and the drawings. Brief Description of Drawings
[00012] The new resources considered characteristic of the illustrative modalities are established in the attached claims. The illustrative modalities, however, as well as a preferred mode of use, objectives and additional resources thereof, will be better understood with reference to the following detailed description of an illustrative modality of the present description when read in conjunction with the attached drawings, in which : Figure 1 is an illustration of a power model, according to an illustrative modality; Figure 2 is an illustration of an electrical energy environment in the form of a block diagram, according to an illustrative embodiment; Figure 3 is an illustration of a plurality of nodes in the form of a block diagram, according to an illustrative embodiment; Figure 4 is an illustration of an agent in the form of a block diagram, according to an illustrative embodiment; Figure 5 is an illustration of an electric energy environment, according to an illustrative modality; Figure 6 is an illustration of an electric energy environment, according to an illustrative modality; Figure 7 is an illustration of a control node according to an illustrative embodiment; an illustrative modality; an illustrative modality; according to an illustrative modality; an energy event in the form of a flowchart, according to an illustrative modality; a device event in the form of a flowchart, according to an illustrative embodiment; a request in the form of a flowchart, according to an illustrative modality; a command, according to an illustrative modality; an illustration of a process for responding to a physical event based on a classification of the event in the form of a flowchart, according to an illustrative modality; Figure 18 is an illustration of a process for responding to a command based on a classification of the command in the form of a flowchart, according to an illustrative embodiment; Figure 19 is an illustration of a process for responding to a request based on a classification of the request in the form of a flow chart; and Figure 20 is an illustration of a data processing system in the form of a block diagram, according to an illustrative embodiment. Detailed Description of the Invention
[00013] Now, in reference to Figure 1, an illustration of a power model is shown, according to an illustrative modality. In this illustrative example, power model 100 is a three-dimensional power model. The power model 100 can be used to model electrical energy in an electrical power grid. More specifically, the power model 100 allows the energy flow, energy management and energy control for an electricity grid to be handled independently of each other.
[00014] As shown, power model 100 includes energy flow plan 102, energy management plan 104 and energy control plan 106. In this illustrative example, energy flow plan 102 includes physical aspects of flow of electrical energy through an electrical power network. These physical aspects include the physical electrical layer 108, thermal physical layer 110 and physical security 112.
[00015] In this illustrative example, the energy management plan 104 and the energy control plan 106 include layers 114, which are part of the Open Systems Interconnection (OSI) model. The Open Systems Interconnection model is a model of a communications architecture and computer network divided into seven layers.
[00016] The energy management plan 104 includes functions performed by a centralized computer system to manage the flow of electrical energy in an electrical energy network. For example, a centralized computer system can communicate with the portion of an electricity network within a boundary to manage the flow of electricity within the boundary.
[00017] A limit provides separation for portions of an electrical power network. The boundary can be, for example, a geographical boundary, an organizational boundary, an administrative boundary, or some other suitable type of boundary. For example, an organizational boundary can separate two portions of an electricity network managed by two different electrical providers.
[00018] The energy control plan 106 includes functions performed by components associated with an electrical power network across multiple organizational boundaries. These components include, for example, processes that run on data processing systems associated with the electricity grid. These processes can communicate autonomously to control the flow of electrical energy through the electrical power network. As used herein, the term "autonomously" means without human control and / or intervention.
[00019] The description of the power model 100 in Figure 1 is intended as an illustration and not as an architectural limitation for the different illustrative modalities. For example, in other illustrative examples, power model 100 may have layers in addition to, or in place of, the different layers shown in power model 100 in Figure 1.
[00020] The illustrative modalities recognize and take into account one or more different considerations. For example, the illustrative modalities recognize and take into account that the techniques currently used to protect computer networks may not work as well on a computer network within an electric power environment.
[00021] For example, the illustrative modalities recognize and take into account that some security solutions currently available can be implemented within a centralized system. However, in other types of architectures, such as, for example, a distributed system, these currently available security solutions may be less efficient than desired. In particular, these currently available solutions may be unable to provide a desired level of security with a desired level of speed and / or efficiency.
[00022] The illustrative modalities recognize and take into account that the solutions currently used for computer networks can be applied to networks in electrical energy environments. These solutions include, for example, message verification integrity, bit counting, data grouping and other known solutions. The illustrative modalities recognize and take into account that these solutions are applied to the energy control plan 106 in the power model 100 for an electric energy environment.
[00023] The illustrative modalities recognize and take into account that there are fewer solutions for the energy management plan 104 and these solutions are not as robust as desired. Currently used techniques include firewalls and systems monitoring.
[00024] The illustrative modalities recognize and take into account that security problems can affect the energy management plan 104, energy control plan 106, or both the energy management plan 104 and the energy control plan 106. These security problems include, for example, cyber attacks that can attack one or both planes.
[00025] The illustrative modalities recognize and take into account which models can be created to protect both plans. These models can connect the energy management plan 104 and the energy control plan 106 through the energy flow plan 102. These models, however, are typically limited to the known types of security problems. For example, models can only identify known types of cyber attacks. These models can take into account only events related to known cyber attacks, such as taking control of part of an electrical power network, interrupting a component, or other events that can occur in known cyber attacks.
[00026] The illustrative modalities recognize and take into account that this type of model, however, in many instances, may not provide a level of security that is as high as desired. These types of models are unable to take into account new types of cyber attacks with events that are not currently known.
[00027] The illustrative modalities also recognize and take into account that many of the techniques currently used to identify security problems are centralized. In other words, information processing typically occurs in one location. As a result, obtaining information can result in the congestion of mobile information within the power grid. Furthermore, the illustrative modalities recognize and take into account that similar events can be treated in the same way, although the origin of these events may be different. In this way, the illustrative modalities provide a method and apparatus to provide security for an electric power network that can be carried out at a level distributed through agents distributed within the electric power network.
[00028] As a result, the illustrative modalities recognize and take into account that it may be desirable to process information generated in the electricity grid to identify events, as well as to classify the events. In event classification, the identification of events that may indicate the presence of a physical attack or potential cyber attack can be performed to increase security to a desired level.
[00029] Now, in reference to Figure 2, an illustration of a block diagram of an electric energy environment is shown, according to an illustrative modality. In this illustrative example, electric power environment 200 includes electric power network 202 and communications network 204. Electric power network 202 is configured for use with power flow plan 102 in Figure 1. Communications network 204 is configured for use with power management plan 104 and / or power control plan 106 in Figure 1.
[00030] As shown in this example, electric power network 202 includes a number of sources 206, a number of loads 208, lines 210 and nodes 212. Electric power network 202 is configured to distribute electric power 214 from a number of sources 206 for a number of charges 208. Lines 210 can be used to distribute electrical power 214 from a number of sources 206 for a number of charges 208. In this illustrative example, lines 210 take the form of power lines streaming. More specifically, lines 210 take the form of electric power lines.
[00031] Two or more lines on lines 210 are connected to a node on nodes 212. Nodes 212 transfer electrical energy 214 transmitted on a line on lines 210 to one or more other lines on lines 210. Nodes 212 include at least a line sensor, a cooperative alternating current flexible transmission system device, an electronic filter, a phase switch, a transformer, an adapter, a processor unit and / or other suitable devices.
[00032] As used herein, the expression "at least one between", when used with a list of items, means that different combinations of one or more of the items listed can be used and only one of each item in the list can be used. required. For example, "at least one between item A, item B and item C" can include, for example, without limitation, item A or item A and item B. This example can also include item A, item B and item C, or item B and item C. In other examples, "at least one in between" can be, for example, without limitation, two from item A, one from item B, and 10 from item C; four from item B and seven from item C; and other suitable combinations.
[00033] In these examples shown, lines 210 and nodes 212 are interconnected on electrical power network 202. In other words, the flow of electrical energy 214 through at least one of lines 210 and / or at least one of nodes 212 can affect the flow of electrical energy 214 through other lines 210 and / or nodes 212. In addition, devices within a node at nodes 212 can affect the flow of electrical energy 214 through other nodes 212.
[00034] In these illustrative examples, communications network 204 is associated with electricity network 202. A first component can be considered associated with a second component when attached to the second component, connected to the second component, attached to the second component, and / or connected to the second component in some other suitable way. For example, a first component can be connected to a second component via wires, wirelessly, or in some other way. The first component can also be connected to the second component via a third component. The first component can also be considered associated with the second component by being part of and / or an extension of the second component.
[00035] Communications network 204 includes data processing systems 216 and communications links 223. Data processing systems 216 are associated with nodes 212. As an example, data processing systems 216 can be connected by wires to nodes 212. In these illustrative examples, each data processing system in data processing systems 216 is associated with a node at nodes 212. In other illustrative examples, only a portion of nodes 212 can be associated with data processing systems 216.
[00036] As shown, agents 218 can be implemented in data processing systems 216. Agents 218 can be implemented using hardware, software, or a combination of the two. In an illustrative example, agents 218 can be processed by software in the form of program code configured to run on 216 data processing systems.
[00037] Agents 218 are associated with at least a portion of nodes 212. This portion can be any or all of nodes 212. In these illustrative examples, each of the agents 218 runs on a different system than the data processing systems 216 on these illustrative examples. In this way, each agent in agents 218 is associated with a node in nodes 212.
[00038] In these examples shown, when a node at nodes 212 is associated with an agent at agents 218, the node is referred to as control node 213. In some illustrative examples, a node at nodes 212 can be associated with more than one agent on agents 218. For example, a data processing system on data processing systems 216 associated with a node on nodes 212 can run more than one of agents 218.
[00039] Communications network 204 allows for the exchange of information between agents 218 that run on data processing systems 216. Furthermore, communications network 204 allows for the exchange of information between a number of processes that run on processing system 219 and agents 218. In these examples, data processing system 219 can be part of operations center 235. Operations center 235 can be located outside the electrical power network 202. An operator at operations center 235 can monitor and / or control the flow of electrical power 214 through electrical power network 202 using communications network 204.
[00040] This exchange of information on communications network 204 takes place using communications links 223 on communications network 204. For example, agents 218 communicate with each other using communications links 223 on communications network 204.
[00041] Communications links 223 may include at least one of lines 210, wireless communications links 225, wired communications links 227, fiber optic cables 229 and other suitable communications links. In addition, the communications network 204 may include other types of devices, such as, for example, without limitation, switches, routers and other suitable types of communications devices. In these examples shown, the communications network 204 can be implemented using an Internet Protocol (IP) network.
[00042] The agents 218 that run on the data processing systems 216 are part of the control system 221 in the electric power environment 200. In other illustrative examples, the control system 221 can include other processes that run on other processing systems of data. These other data processing systems can be located inside and / or outside the electrical power network 202. For example, the control system 221 can include the data processing system 219 in the operations center 235.
[00043] In these illustrative examples, the control system 221 is configured to control the flow of electrical energy 214 through the electrical energy network 202 using agents 218. More specifically, each agent in agents 218 controls the flow of electrical energy through the node at nodes 212 associated with the agent.
[00044] In these illustrative examples, agents 218 in control system 221 communicate with each other using communications network 204 to form circuit 220. Circuit 220 is a virtual power circuit 222 in these examples. The virtual power circuit 222 includes the energy flow circuit 242 and the energy control circuit 244. The energy flow circuit 242 is formed within the electrical power network 202. Furthermore, the energy flow circuit 242 operates within of the power flow plan 102 in Figure 1. The power control circuit 244 is formed within the communications network 204. The power control circuit 244 operates with the power control plan 106 in Figure 1.
[00045] The energy flow circuit 242 is formed in the electrical power network 202 by the first endpoint 230, second endpoint 232, plurality of nodes 224 at nodes 212, and a number of lines 233 on lines 210. The first endpoint 230 can be selected from a source in a number of sources 206 and a node in a plurality of nodes 224. The second endpoint 232 can be selected from a load in a number of loads 208 and one node in the plurality of nodes 224.
[00046] The first endpoint 230, second endpoint 232 and plurality of nodes 224 are connected by a number of lines 233 on lines 210. Virtual power circuit 222 carries portion 231 of electrical energy 214 in the power grid electrical 202 on a number of lines 233 in these examples. The portion 231 may be some or all of the electrical energy 214, depending on the configuration of the virtual power circuit 222.
[00047] The power flow circuit 242 in the virtual power circuit 222 can share the components with a number of other energy flow circuits in the electrical power network 202. As an illustrative example, the power flow circuit 242 can share at least a portion of the number of lines 233 with another power flow circuit.
[00048] For example, a portion of the electrical energy that flows in a number of 233 lines may or may not have the same starting point as another portion of the electrical energy that flows in a number of 233 lines. In addition, a portion of the electrical energy that flowing on a number of lines 233 may or may not be distributed to the same endpoint as another portion of the electrical energy flowing on a number of lines 233. These different portions of electrical energy flowing on a number of lines 233 may be indistinguishable from each other the others. Furthermore, these different portions of electrical energy flowing in a number of lines 233 can be indistinguishable in the energy flow plane 102 in Figure 1.
[00049] In these examples shown, the plurality of nodes 224 is selected by agents 218 as a group. For example, one, some or all of the agents 218 select the plurality of nodes 224. In other words, the plurality of nodes 224 for the virtual power circuit 222 is selected by at least a portion of the agents 218 in the control system 221. At least a portion of agents 218 communicate with each other to identify a number of agents 226 in agents 218 associated with the plurality of nodes 224.
[00050] A number of agents 226 runs on a number of data processing systems 228 associated with the plurality of nodes 224. A number of agents 226 running on a number of data processing systems 228 forms the power control circuit 244 in the virtual power circuit 222.
[00051] In these examples, the locations of a number of data processing systems 228 in the power control circuit 244 can follow the locations of the plurality of nodes 224 in the energy flow circuit 242 in the electrical power network 202. In others In other words, power control circuit 244 may resemble power flow circuit 242 in these examples.
[00052] A number of agents 226 configure the plurality of nodes 224 that are part of the energy flow circuit 242 in the virtual power circuit 222. This configuration of the plurality of nodes 224 can be based on a number of policies for a number of agents 226. In some instances, an agent in a number of agents 226 may use more than one policy.
[00053] Furthermore, the configuration of the plurality of nodes 224 includes using communications network 204 to select a number of lines 233 and reserve a capacity in a number of lines 233 for the distribution of portion 231 of electrical energy 214 through the plurality of nodes 224. A number of agents 226 in the energy control circuit 244 monitors and controls the distribution and flow of portion 231 of electrical energy 214 through a number of lines 233 and the plurality of nodes 224 in the energy flow circuit 242 .
[00054] A line in an energy flow circuit can transmit different electrical energy flows 214 to different energy flow circuits formed within the electrical energy network 202. Different energy control circuits within the communications network 204 allows these different flows of electrical energy 214 carried on the line are distinguished from each other in the energy control plane 106 in Figure 1. In other words, each energy control circuit monitors and controls the flow of electrical energy 214 to a flow circuit of particular energy.
[00055] The illustration of the electric energy environment 200 in Figure 2 does not mean to imply physical or architectural limitations to the way in which different illustrative modalities can be implemented. Components other than and / or in place of those illustrated can be used. Some components may be unnecessary in some illustrative modalities. Also, the blocks are presented to illustrate some functional components. One or more of these blocks can be combined and / or divided into different blocks when implemented in different illustrative modalities.
[00056] For example, the control process 238 in the control system 221 can run in the data processing system 219 located outside the electrical power network 202. The control process 238 can communicate with agents 218 through links of wireless communications 225. Control process 238 can select a number of agents 226 on agents 218 for power control circuit 244. In addition, control process 238 can send commands to a number of agents 226 that configure the plurality of nodes 224 to form part of the energy flow circuit 242.
[00057] Still, in other illustrative embodiments, agents 218 may run on processor units 240 at nodes 212. For example, processor units 240 may be part of different devices at nodes 212.
[00058] Now, in reference to Figure 3, an illustration of a block diagram of a plurality of nodes is shown, according to an illustrative modality. In this illustrative example, the plurality of nodes 300 is an example of an implementation for the plurality of nodes 224 in Figure 2. The plurality of nodes 300 is part of a circuit in an electricity network, such as circuit 220 in the network electrical power 202 in Figure 2.
[00059] As shown, the plurality of nodes 300 includes node 302. Node 302 is located at the connection of power line 301 and power line 303. Node 302 includes line sensor 306, line sensor 307, control device 308, control device 309 and processor unit 310. Line sensor 306 and control device 308 are located on power line 301. Line sensor 307 and control device 309 are located on line energy 303.
[00060] In this illustrative example, processor unit 310 can be implemented in a number of different devices, such as, a data processing system, a node, a sensor, or some other suitable device. For example, the data processing system may be a data processing system in data processing systems 216 in Figure 2. Examples of processor unit 310 include a digital signal processor, a controller, a central processing unit , a multi-core processor, or some other similar type of hardware component. Processor unit 310 is configured for communications with line sensor 306, line sensor 307, control device 308 and control device 309.
[00061] As shown, agent 318 runs on processor unit 310. In an illustrative example, agent 318 is implemented in software. Of course, Agent 318 can also be implemented on hardware or a combination of the two. In other words, one or more processes performed by the agent 318 can be implemented using circuits instead of the software running on processor unit 310 in some illustrative embodiments.
[00062] As shown, agent 318 monitors, tracks and controls the flow of electrical energy 316 through node 302. Agent 318 includes a number of processes. These processes include at least one among the control device interface process 321, demand and response system interface process 323, optimization process 325, stabilization process 327, energy flow signaling process 329, announcement process 331, cybersecurity process 333 and other processes. In this illustrative example, the cybersecurity process 333 can process information to identify and classify events according to an illustrative modality.
[00063] The different agents associated with the plurality of nodes 300 can be configured to perform different operations, depending on the processes within the different agents. For example, some agents can be configured to perform only a single operation, while other agents can be configured to perform four or five different types of operations.
[00064] When agent 318 includes control device interface process 321, demand and response system interface process 323, optimization process 325, stabilization process 327, energy flow signaling process 329, announcement 331 and cyber security process 333, agent 318 is referred to as the intelligent energy gateway agent 320.
[00065] The intelligent energy gateway agent 320 can have more memory, more computing resources, and faster data transmission rates when compared to other types of agents. The Intelligent Power Gateway Agent 320 can be found at selected locations on an electrical power network. These locations are selected to reduce latencies in the exchange of information, optimize the use of data, coordinate the nodes in the plurality of 300 nodes for load balancing, and reduce the bandwidth used in the exchange of information.
[00066] In this illustrative example, line sensor 306 and line sensor 307 are configured to send information 319 about a number of parameters to power line 301 and power line 303, respectively, to agent 318. The information 319 include, for example, the capacity for the power line, voltage and / or other appropriate information. A capacity for the power line can be a thermal capacity. In addition, this capacity can vary in relation to the time.
[00067] Information 319 can be sent to agent 318 using a communications network, such as communications network 204 in Figure 2. Information 319 is sent to agent 318 in response to an event. This event can be, for example, without limitation, a request for information 319, the result of a period of time, the beginning of a cycle in a signal, or some other suitable event. A request for 319 information can be made in response to a request for a service received by the 318 agent. The service may include, for example, without limitation, data conversion, the generation of alerts, the provision of an interface for exchanging information. information, and / or other appropriate operations.
[00068] Agent 318 performs determinations on the flow of electrical energy through node 302 using information 319. Agent 318 sends commands 322 to control device 308 and / or control device 309 based on these determinations. Control device 308 and control device 309 are cooperative alternating current flexible transmission system (FACTS) devices in this illustrative example. Control device 308 and control device 309 are configured to alter the flow of electrical energy 316 through node 302 in response to receiving commands 322.
[00069] In this illustrative example, agent 318 stores information 319 in database 324 on processor unit 310. Database 324 is a collection of information. In addition, database 324 can be comprised of a number of processes and / or interfaces for accessing the collection of information.
[00070] Database 324 can be updated with information 319 when information 319 is received by agent 318. In other illustrative examples, database 324 can be updated based on an event. The event can be, for example, without limitation, the result of a period of time, receipt of a request for an update in the database 324 or some other suitable event.
[00071] Database 324 is the distributed database 341 in these examples. The distributed database 341 contains information for other nodes in the plurality of nodes 300 in addition to node 302. The distributed database 341 can be associated with all or part of the plurality of nodes 300 in this illustrative example. For example, agent 318 can send information 319 stored in the distributed database 341 on node 302 to other agents on other nodes in the plurality of nodes 300. These other agents can store information 319 in the databases associated with these other nodes. These databases are substantially the same as the distributed database 341 in these illustrative examples.
[00072] Furthermore, in these illustrative examples, the distributed database 341 can be distributed across organizational boundaries. In this way, at least a portion of the agents for the plurality of nodes 300 can exchange information across organizational boundaries to create and / or update the distributed database 341.
[00073] As an illustrative example, agent 326 runs on processor unit 328 associated with node 330 in the plurality of nodes 300. Agent 326 receives information 332 and stores information 332 in database 324 on processor unit 328. Agent 326 also sends information 332 to agent 318 using a communications network, such as communications network 204 in Figure 2. Agent 318 then stores information 332 in database 324 stored on the processor unit 310. In this way, the plurality of nodes 300 can update database 324 autonomously.
[00074] Information is stored in database 324 based on a number of factors. These factors may include, for example, without limitation, the type of information, the quality of information, a period of time for storage, the availability of storage space in the 324 database, and other suitable factors. Storing information 319 in database 324 can also be based on latency and / or throughput of the communications network used by different agents.
[00075] In these illustrative examples, agents associated with the plurality of nodes 300 exchange information using standard TCP / IP network protocols. However, in some illustrative examples, agents can exchange information using moving objects. These moving objects are information containing program code. This information can include information for the node, such as capacity information, routing information and / or other appropriate information. This information may also include, for example, program code for a new process, new rules and / or policies, software updates and / or other suitable types of information.
[00076] Moving objects can be sent to agent 318 from an operations center. Agent 318 reads the moving object and stores the information within the moving object. The moving object is cloned. Agent 318 sends these clones to other agents.
[00077] The illustration of the plurality of nodes 300 in Figure 3 does not mean to imply physical or architectural limitations to the way in which different illustrative modalities can be implemented. Components other than and / or in place of those illustrated can be used. Some components may be unnecessary in some illustrative modalities. Also, the blocks are presented to illustrate some functional components. One or more of these blocks can be combined and / or divided into different blocks when implemented in different illustrative modalities.
[00078] For example, in some illustrative embodiments, processor unit 310 can be part of data processing system 334. Data processing system 334 can be connected to node 302 instead of being included in node 302. In other illustrative embodiments, processor unit 310 may form part of control device 308 and / or control device 309 at node 302.
[00079] In other illustrative modalities, the power lines, in addition to the power line 301 and the power line 303, can be connected to node 302.
[00080] In still other illustrative examples, sensors in addition to, or in place of, line sensor 306 and / or line sensor 307 can be associated with power line 301 and / or power line 303. These sensors can be configured to detect parameters, such as, for example, without limitation, temperature, current flow, power phase, line voltage, a location for the power lines, and / or other parameters suitable for the power lines.
[00081] In some illustrative examples, database 324 can be found on a storage device connected to the plurality of nodes 300. For example, database 324 can be found on a storage device that can be accessed by agent 318 and other agents associated with other nodes in the plurality of nodes 300 using wireless communications links.
[00082] Now, in reference to Figure 4, an illustration of an agent is shown in the form of a block diagram, according to an illustrative modality. In this example shown, agent 400 is an example of an implementation for an agent on agents 218 in Figure 2. In some cases, agent 400 can be agent 318 in Figure 3. Agent 400 can be implemented using hardware, software, or a combination of the two.
[00083] As shown, agent 400 comprises classifier 402 and analyzer 404. Classifier 402 is configured to receive information and process information 406. Information 406 can be received, for example, without limitation, from one or more sensors associated with electrical network 202 in Figure 2, a computer system configured to communicate wirelessly with agent 400 using communications network 204 in Figure 2, or some other source.
[00084] In some illustrative examples, this information may include an identification of event 408. In other illustrative examples, agent 400 can be configured to identify event 408 using information 406.
[00085] In these illustrative examples, event 408 can be one between physical event 410 and cyber event 412.0 physical event 410 is an event that occurs within the electrical power network 202 in Figure 2. For example, physical event 410 can be an event that occurs in relation to one or more devices in the electrical power network 202. In some cases, physical event 410 may be a change in a parameter for a component of the electrical power network 202.
[00086] As shown, physical event 410 can take the form, for example, without limitation, of switching event 414, of energy event 416, of device event 418, or some other type of physical event. Switching event 414 is an event that affects connections between components within the electrical power network 202. For example, switching event 414 can be a connection or disconnection of a load, a power source or some other suitable type component within the electrical power network 202.
[00087] The energy event 416 is an event that refers to the energy in the electricity grid 202. The energy event 416 can be, for example, without limitation, a change in energy demand, a change in energy production , a change in energy distribution, a change in energy consumption, or some other appropriate type of event related to the state of energy within the electrical power network 202. In addition, energy event 416 may be a voltage reduction over a power line, a change in energy availability from a renewable energy source, a change in energy availability from a storage source, a rerouting of the energy flow through one or more power lines in the 202 power grid, or some other suitable type of event.
[00088] As shown, device event 418 is an event that refers to the state of devices in the electrical power network 202. Device event 418 can be, for example, without limitation, the reconfiguration of a protective device, activation of a protection device, deactivation of a protection device, reconfiguration of a routing device, or some other suitable type of event that refers to one or more devices in the electrical power network 202.
[00089] In these illustrative examples, a protection device can be, for example, a fuse, a grounding system, a circuit breaker, a power relay, or some other type of device configured to protect a portion of the electric power network 202 A routing device can be, for example, a relay, a transformer, a reactor, or some other suitable type of device used to route energy.
[00090] Cyber event 412 is an information event or a computer based event. For example, cyber event 412 can take the form of message 420. Message 420 can be information of any kind. In an illustrative example, message 420 may take the form of command 422, request 424, or some other suitable type of information.
[00091] Command 422 can be a guideline for agent 400 to perform an action within the electrical power network 202. Command 422 can also be referred to as a request for an action to be performed. Request 424 can be a request for information acquired by agent 400 and / or one or more other agents. In some cases, the processing of command 422 and request 424 may result in an action that, in turn, results in an event, such as, for example, without limitation, event 408. Thus, message 420 can also be a cause of an event.
[00092] In these illustrative examples, classifier 402 is configured to classify event 408. In an illustrative example, classifier 402 classifies event 408 as a normal expected event 430, abnormal expected event 432, normal unexpected event 434, abnormal unexpected event 436 or some other appropriate classification for an event.
[00093] Event 408 is classified as expected normal event 430 when event 408 is an event that generally occurs and is expected from the operation of the 202 power grid. The expected normal event 430 may include, for example, without limitation , at least connecting a load, disconnecting a load, connecting a power source, disconnecting a power source, reconfiguring a power routing device, activating or deactivating a switch during a scheduled maintenance activity, an energy fluctuation within the selected tolerances and / or that lasts less than a selected time limit, and other suitable types of normal expected events.
[00094] Event 408 is classified as an expected abnormal event 432 when event 408 does not occur during normal operation of the electric power network 202, however, it is expected during the operation of the electric power network 202. The expected abnormal event 432 can include, for example, without limitation, at least a voltage flicker, a short circuit, an insulation break, a backup operation initiation, harmonic distortion, a power cut, a voltage reduction, an interruption, an emergency event, and other suitable types of abnormal expected events.
[00095] In addition, event 408 is classified as the normal unexpected event 434 when event 408 is not expected to occur during normal operation of the electricity grid 202, however, it is within the tolerances stored for normal operation of the grid of electrical energy 202. In other words, the normal unexpected event 434 is an event that is within the operational limits for the normal operation of the electrical energy network 202, however, this is not expected.
[00096] The normal unexpected event 434 may include, for example, without limitation, at least an increase in energy consumption, an increase in energy generation, a re-routing of the energy flow and other suitable types of normal unexpected events. Normal unexpected events can be within selected, but unexpected, limits based on sensor data from the 202 power grid.
[00097] Event 408 is classified as an unexpected abnormal event 436 when event 408 is an event that generally does not occur and is not expected to occur during the operation of the 202 power grid. The unexpected unexpected event 436 may include, for example, example, without limitation, at least one being a cyber security breach, a hostile invasion of communications network 204 associated with electrical network 202, stolen equipment, damaged equipment, and other types of abnormal unexpected events.
[00098] The 404 analyzer on agent 400 is configured to determine whether to start a number of 438 actions based on the classification of event 408. In particular, the 404 analyzer can identify the appropriate number of 438 actions that need to be taken with based on the classification of event 408 and in some cases initiate a number of 438 actions in response to a determination that a number of 438 actions should be initiated.
[00099] In some illustrative examples, analyzer 404 can be configured to reclassify event 408 after classifier 402 has already classified event 408. For example, in some cases, analyzer 404 may reclassify message 420 that has been classified as normal unexpected event 434. In other illustrative examples, analyzer 404 may determine that a particular classification for event 408 is inappropriate and may request that classifier 402 reclassify event 408.
[000100] As shown, classifier 402 and analyzer 404, when implemented in software, can be implemented as separate processes, within the same process, or part of one or more other processes that run on agent 318 in Figure 3. For example, classifier 402 and analyzer 404 can be implemented in the cybersecurity process 333, as shown in agent 318 in Figure 3.
[000101] In this way, when agents 218 are implemented in a similar way to agent 400, the classification of physical events and cyber events that occur within the electrical energy environment 200 can occur in a distributed manner throughout the electrical energy network 202 and communications network 204. Furthermore, this type of determination of classification of response actions for events that use agents 218 distributed throughout the electrical power network 202 can allow events to be classified and manipulated more quickly when compared to carrying out these operations in a centralized system within the electric power network 202. In addition, when an agent in agents 218, such as agent 400, is unable to perform the classification of an event or determine response actions for the event, an agent neighboring agent 400 may be able to perform these operations.
[000102] The illustration of agent 400 in Figure 4 does not mean to imply physical or architectural limitations to the way in which different illustrative modalities can be implemented. Components other than and / or in place of those illustrated can be used. Such components may be unnecessary in some illustrative modalities. Also, the blocks are presented to illustrate some functional components. One or more of these blocks can be combined and / or divided into different blocks when implemented in different illustrative modalities.
[000103] For example, in some cases, classifier 402 may be configured to classify event 408 as a particular type of event that is different from the different classifications for event 408 shown in Figure 4. In addition, in some illustrative examples, the classifier 402 and analyzer 404 can be part of the same process.
[000104] In other illustrative examples, different classifications can be used for event 408. For example, event 408 can be classified only as to whether event 408 is expected or unexpected.
[000105] Now, in reference to Figure 5, an illustration of an electric energy environment is shown, according to an illustrative modality. In this illustrative example, the electric power environment 500 is an example of an implementation for the electric power environment 200 in Figure 2. Electric power environment 500 includes electric power network 502. Electric power network 502 is an example of an implementation for the electricity grid 202 in Figure 2.
[000106] In this illustrative example, the electrical network 502 has the limit 504. The limit 504 separates the portion 506 of the electrical network 502 from the portion 508 of the electrical network 502. In addition, the limit 504 prevents the management of coordinated energy of portion 506 and portion 508. For example, threshold 504 may be a geographical boundary, an organizational boundary, an administrative boundary, or some other suitable type of boundary.
[000107] As an illustrative example, portion 506 of electrical network 502 can be managed by operations center 507, while portion 508 of electrical power 502 can be managed by operations center 510. Operations center 507 and operations center 510 may not be able to coordinate power management for electrical power network 502 in this example.
[000108] As shown, operations center 507 can include data processing system 509 operated by operator 511. Operations center 510 can include data processing system 513 operated by operator 515. In this illustrative example, the network of power 502 includes generator 512 and load 514. Generator 512 is an example of an implementation for a source in a number of sources 206 in Figure 2. Load 514 is an example of an implementation for a load in a number of loads 208. Load 514 can be household, industrial, business, tool, or some other suitable type of cargo. The electrical power network 502 is configured to distribute the energy supplied by the generator 512 to the load 514.
[000109] Electricity network 502 also includes nodes 516, 518, 520, 522, 524 and 526 together with power lines 528, 530, 532, 534, 536, 538, 540, 542, 544 and 545. Nodes 516, 518, 520, 522, 524 and 526 include control devices 517, 519, 521, 523, 525 and 527. These control devices are cooperative alternating current flexible transmission system (FACTS) devices in this example illustrative. However, in other illustrative examples, these control devices can be power semiconductor devices or other suitable types of devices.
[000110] In addition, node 516 includes line sensor 529 located on power line 530 and line sensor 531 located on power line 532. Node 518 includes line sensor 533 located on power line 534 and the line sensor 535 located on power line 538. node 520 includes line sensor 572 located on power line 536 and line sensor 537 located on power line 540. node 522 includes line sensor 539 located on power line 542. Node 524 includes line sensor 541 located on power line 544.
[000111] In this illustrative example, nodes 516, 518, 520, 522, 524 and 526 are connected to data processing systems 546, 548, 550, 552, 554, and 556, respectively. Agents 558, 560, 562, 564, 566 and 568 run on data processing systems 546, 548, 550, 552, 554 and 556, respectively. These agents control the flow of electrical energy through nodes 516,518, 520, 522, 524 and 526. In particular, agents use a number of policies to control the flow of electrical energy through nodes.
[000112] Agents 558, 560, 562, 564, 566 and 568 can communicate autonomously with each other using the communications links, such as communications links 223 in Figure 2. These communications links are power lines 528, 530, 532, 534, 536, 538, 540, 542, 544 and 545 in this illustrative example. In particular, these communications links take the form of broadband along power lines. Agents 558, 560, 562, 564, 566 and 568 communicate with each other to form the virtual power circuit 570.
[000113] Virtual power circuit 570 includes energy flow circuit 571 and energy control circuit 573. Energy flow circuit 571 includes generator 512, node 516, node 518, node 524, node 526, load 514 and power lines 528, 530, 532, 538, 542 and 544. Power lines 528, 530, 532, 538, 542 and 544 connect generator 512, node 516, node 518, node 524, node 526 and load 514. The energy flow circuit 571 in virtual power circuit 570 is configured to distribute the electrical energy from generator 512 to load 514.
[000114] The power control circuit 573 in the virtual power circuit 570 includes agents 558, 560, 564 and 568 associated with nodes 516, 518, 524 and 526, respectively. The power control circuit 573 monitors and controls the flow of electrical energy from generator 512 through nodes 516, 518, 524 and 526 and up to load 514.
[000115] In this illustrative example, agent 558 and agent 568 are configured to perform a greater number of operations than agents 560, 562, 564 and 566. For example, agent 558 and agent 568 can be gate agents. intelligent power inputs, such as, intelligent power input port agent 320 in Figure 3.
[000116] In this example shown, agent 558 and agent 568 can exchange information with operations center 507 and operations center 510, respectively. This exchange of information allows operator 511 in operations center 507 and operator 515 in operations center 510 to manage portion 506 and portion 508, respectively, of the power grid 502 using agent 558 and agent 568, respectively .
[000117] Furthermore, the virtual power circuit 570 includes components from both the 506 portion and the 508 portion of the 502 power grid. The different agents within the power control circuit 573 in the virtual power circuit 570 are selected to exchange information across the 504 limit.
[000118] For example, agent 560 and agent 564 are selected to exchange information over limit 504. Agent 562 and agent 566 are selected to exchange information over limit 504. In these illustrative examples, these agents exchange information to create and / or updating a distributed database, such as the distributed database 341 in Figure 3.
[000119] Now, in reference to Figure 6, an illustration of an electric energy environment is shown, according to an illustrative modality. In this illustrative example, electric power environment 600 is an example of an implementation of electric power environment 200 in Figure 2. Electric power environment 600 includes electric power network 602.
[000120] In this illustrative example, electric power network 602 includes generator 604, generator 605, generator 606, load 608, load 610, node 612, node 614, node 616, node 618, power line 620 , power line 622, power line 624, power line 626, power line 628, power line 630, power line 632, power line 634 and power line 635.
[000121] Nodes 612, 614, 616 and 618 include control devices 613, 615, 617 and 619, respectively. These control devices are cooperative alternating current flexible transmission devices in this example. In addition, node 612 includes line sensor 621 located on power line 624 and line sensor 623 located on power line 626. node 614 includes line sensor 625 located on power line 628. Node 616 includes line sensor 627 located on power line 630. Node 618 includes line sensor 629 located on power line 632 and power line 634.
[000122] As shown in this example, nodes 612, 614, 616 and 618 are connected to data processing systems 636, 638, 640 and 642. Agents 644, 646, 648 and 650 execute on data processing systems 636 , 638, 640 and 642, respectively. Agents 644, 646, 648 and 650 are associated with nodes 612, 614, 616 and 618, respectively. These agents control the flow of electrical energy through the nodes.
[000123] Furthermore, agents 644, 646, 648 and 650 communicate autonomously with each other using communications network 652. Communications network 652 is an example of an implementation for communications network 204 in Figure 2. A communications network 652 provides communications over wireless communications links in this illustrative example.
[000124] Generators 604, 605 and 606 can also use communications network 652 to communicate with agents 644, 646, 648 and / or 650. Line sensors 621, 623, 625, 627 and 629 use the network communications 652 to exchange information with agents 644, 646, 648 and 650.
[000125] A number of virtual power circuits can be formed in the electrical power network 602 to provide the power provided by at least one of the generators 604, 605 and 606 to at least one between load 608 and load 610. For example , the first virtual power circuit 660 may include generator 605, load 608, load 610, node 612, node 614, node 618, power line 622, power line 624, power line 628, power line 632 and power line 634. Agents 644, 646 and 650 configure nodes 612, 614 and 618 to meet in the first virtual power circuit 660.
[000126] The second virtual power circuit 662 may include generator 604, load 608, load 610, node 612, node 616, node 618, power line 620, power line 626 and power line 630. The agents 644, 648 and 650 configure nodes 612, 616 and 618 to meet in the virtual power circuit 662.
[000127] The third virtual power circuit 664 may include generator 604, load 608, load 610, node 612, node 616, node 618, power line 620, power line 626 and power line 630. The agents 644, 648 and 650 configure nodes 612, 616 and 618 to meet on the third virtual power circuit 664. As shown, power line 620, power line 626 and power line 630 carry the flows of electricity both for the second virtual power circuit 662 and for the third virtual power circuit 664.
[000128] The flow of electrical energy is different in the second virtual power circuit 662 and in the third virtual power circuit 664. A first portion of the electrical energy flowing in the power lines 620, 626 and 630 serves for the second power circuit virtual 662. A second portion of the electrical energy flowing in the 620, 626 and 630 power lines serves for the third virtual power circuit 664. However, these portions of electrical energy in the 620, 626 and 630 power lines for each of these virtual power circuits are indistinguishable in the energy flow plan 102 in Figure 1.
[000129] Agents 644, 648 and 650 in the second virtual power circuit 662 and in the third virtual power circuit 664 are able to distinguish between these flows of electrical energy through the power lines 620, 626 and 630. Furthermore, the agents 644, 648 and 650 track, monitor and control these multiple flows of electrical energy. In this way, virtual power circuits can be used to charge the balance of the flow of electrical energy through the electrical power network 602.
[000130] The illustrations of the electric energy environment 500 in Figure 5 and the electric energy environment 600 in Figure 6 are not intended to imply physical or architectural limitations in the way in which the different illustrative modalities can be implemented. For example, in some illustrative embodiments, the communications network 652 can provide communications over the power lines on the 502 power grid. In other words, information can be exchanged using these power lines instead of the wireless communications links. .
[000131] Now, in reference to Figure 7, an illustration of a control node is shown, according to an illustrative modality. In this illustrative example, control node 700 is an example of an implementation of a node at nodes 212 in Figure 2. In addition, control node 700 is an example of an implementation for node 302 in Figure 3.
[000132] As shown in this example, power line 701 and power line 703 are connected to control node 700. Control node 700 includes line sensor 702, line sensor 704, control device 706, device control 708, switch 710 and processor unit 712 in this illustrative example. Agent 713 runs on processor unit 712.
[000133] Line sensor 702 and control device 706 are located on power line 701. Line sensor 704 and control device 708 are located on power line 703. Control device 706 and control device control 708 are cooperative alternating current flexible transmission system devices (FACTS) in this illustrative example.
[000134] Line sensor 702 and line sensor 704 are configured to capture a number of parameters for power line 701 and power line 703, respectively. These parameters may include, for example, without limitation, electrical power capacity, temperature, current flow, power phase, line voltage, a location of the power lines and other parameters suitable for the power lines. In these examples, line sensor 702 and line sensor 704 are configured to store information for a number of parameters.
[000135] In this illustrative example, switch 710 allows line sensor 702, line sensor 704, control device 706, control device 708 and agent 713 that run on processor unit 712 to communicate with each other within the control 700. For example, line sensor 702 and line sensor 704 are configured to send information for a number of parameters to power line 701 and power line 703, respectively, to processor unit 712 via of switch 710.
[000136] In this illustrative example, agent 713 running on processor unit 712 receives information for a number of parameters sent from line sensor 702 and line sensor 704 via switch 710. Agent 713 sends commands to the control device 706 and / or control device 708 based on the information received.
[000137] In these illustrative examples, agent 713 can make determinations as to whether the flow of electrical energy through power line 701 and / or power line 703 is within a desired limit. Based on these determinations, agent 713 can send commands to the control device 706 and / or control device 708 to control the flow of electrical energy through the control node 700.
[000138] In this illustrative example, agent 713 running on processor unit 712 can exchange information with other agents associated with other control nodes. The exchange of information includes at least one between sending and receiving information. For example, agent 713 can send information to agent 715 that runs on processor unit 714 and / or agent 717 that runs on processor unit 716. Processor unit 714 and processor unit 716 are associated with a node different control.
[000139] In this example shown, the information exchanged between agent 713, agent 715 and / or agent 717 can be stored in a distributed database, such as, the distributed database 341 in Figure 3.
[000140] In other illustrative examples, processor unit 712 may not be located at control node 700. For example, processor unit 712 may be implemented in a data processing system connected to control node 700.
[000141] Now, in reference to Figure 8, an illustration of an agent is shown, according to an illustrative modality. In this illustrative example, agent 800 is an example of an implementation for an agent in agents 218 in Figure 2 and / or agent 318 in Figure 3. In addition, agent 800 can be part of a virtual power circuit, such as a circuit of virtual power 222 in Figure 2.
[000142] Agent 800 includes the 802 power control plan interface, the 804 power management plan interface, and the 806 power flow plan interface. These interfaces can be, for example, Ethernet interfaces. The 802 power control plan interface allows communications between agent 800 and other agents on an electrical power network. The 804 power management plan interface allows communications between agent 800 and an operations center. The 806 power flow plan interface allows communications between agent 800 and devices included in a node associated with agent 800. Devices at the node can include, for example, a number of cooperative alternating current flexible transmission system devices , a number of line sensors and other suitable devices.
[000143] Agent 800 includes energy flow signaling process 808, announcement process 810, optimization process 812, stabilization process 814 and demand and response interface process 816. These processes allow agent 800 to perform operations within the power control plane 106 in Figure 1.
[000144] In this illustrative example, the energy flow signaling process 808 sends the request for capacity 818 to a control device on the node associated with agent 800 using the energy flow plan interface 806. The control device can be , for example, the cooperative alternating current flexible transmission system device. The control device sends message 820 to the energy flow signaling process 808 to indicate that the request will be granted.
[000145] The 808 energy flow signaling process also sends and / or receives requests for capacity 822 to and / or from other agents. In addition, the energy flow signaling process 808 sends and / or receives messages 824 to and / or from other agents indicating that requests for capacity 822 will be granted. These agents are associated with nodes that can be found, for example, along a path between an energy source and a load.
[000146] The 810 announcement process receives 826 information from the line sensor. The announcement process 810 stores the information 826 in a database, such as the distributed database 341 in Figure 3. In addition, the announcement process 810 sends announcement 828 to other agents. Ad 828 includes 826 information. Other agents can then store 826 information in substantially similar databases. Information 826 may include, for example, without limitation, a power line capacity connected to the node associated with agent 800, bus voltage, power flow, phase angle, and / or other suitable information.
[000147] In this illustrative example, the optimization process 812 receives traffic engineering data 830 from the advertising process 810. Traffic engineering data 830 includes at least a portion of the information 826 in this example, as well as other information appropriate. For example, traffic engineering data 830 includes the flow of through energy and the capacity of lines connected to the node associated with agent 800, as well as other appropriate information.
[000148] The optimization process 812 also receives the virtual power circuit path information 832 from the other agents associated with other nodes. The virtual power circuit path information 832 includes information, such as, for example, the flow of through energy and the capacity for other nodes and lines that are not part of the virtual power circuit in which agent 800 is included.
[000149] The optimization process 812 uses traffic engineering data 830 and virtual power circuit path information 832 to optimize the flow of electrical energy through an electrical power network. For example, the optimization process 812 can ensure that the node associated with agent 800 is in a virtual power circuit. This virtual power circuit is used to charge the balance of the energy flow within the electrical power network, so that the electrical energy flow through the power lines in the electrical power network is not greater than a capacity for the power lines. energy.
[000150] In addition, this optimization of the flow of electricity through the 812 optimization process reduces energy loss within the electricity network, reduces a cost of energy distribution within the electricity network and reduces congestion in the electricity network. electricity. In addition, this optimization also protects the control devices from operating outside the safety limits and increases the energy flow in relation to the capacity of the electric power network. In these examples, a cost is a financial cost.
[000151] The optimization process 812 exchanges optimization information 834 with the energy flow signaling process 808. The energy flow signaling process 808 can use the optimization information 834 to configure the node associated with agent 800 for optimization of the virtual power circuit. In addition, the optimization process 812 also sends optimization information 836 to the other agents in the virtual power circuit. The other agents can then use the 836 optimization information to configure the other nodes associated with other agents for optimization.
[000152] Optimization information 836 may include, for example, a configuration for a number of virtual power circuits in the power grid that uses the capacity of the power lines in the power grid with a desired efficiency.
[000153] Stabilization process 814 receives stability information 838 from a number of devices on the node associated with agent 800. Stability information 838 can include values for a number of parameters for the number of devices. For example, stability information 838 may include voltage data, reactive volt-ampere (VAr) data, and other suitable types of data for the node.
[000154] For example, the stability information 838 may indicate the presence of unwanted fluctuations in the distribution of electrical energy through the node. The 840 commands can be sent to a control device at the node to configure the control device to maintain a substantially desired distribution of electrical energy through the node.
[000155] In addition, the stabilization process 814 also sends stability information 839 to the announcement process 810. The announcement process 810 can store stability information 838 in the database. In addition, the announcement process 810 can send the stability information 839 to the other agents to be stored in the substantially similar databases.
[000156] The demand and response interface process 816 communicates with an operations center, such as operations center 507 and / or operations center 510 in Figure 5. This communication takes place through the management plan interface energy 804. An operator at the operations center can send request 842 for information to the 816 demand and response interface process. This information can occur from a number of devices on the node and / or from other devices on other we. The demand-response interface process 816 sends message 844 indicating that request 842 will be granted.
[000157] The demand and response interface process 816 sends a request for capacity 846 to the process of signaling energy flow 808. In response to receiving the request for capacity 846, the process of signaling energy flow 808 sends the request for capacity 818 for a control device on the node associated with agent 800 and requests for capacity 822 for other agents. In particular, requests for capacity 822 are sent to a number of agents along a path between a power source and a load on the power grid. This number of agents can be used to configure the nodes associated with a number of agents to be on a virtual power circuit.
[000158] In this example shown, the node associated with agent 800 and the nodes associated with a number of agents send message 820 and messages 824, respectively, to the energy flow signaling process 808. These messages indicate that the request for capacity 818 and requests for 824 messages will be granted. In other words, these messages indicate that the nodes are available and have the capacity to be part of the virtual power circuit.
[000159] In response to receiving message 820 and messages 824, the energy flow signaling process 808 sends message 847 to the demand and response interface process 816 which indicates that the request for information will be granted.
[000160] In some illustrative examples, agent 800 takes the form of an intelligent energy gateway agent, such as intelligent energy gateway agent 320 in Figure 3. In these examples, the interface process of demand and response 816 is used to exchange information with other intelligent energy gateway agents.
[000161] For example, the 816 demand and response interface process can send the request for 850 energy to another intelligent energy gateway agent through the 802 power control plan interface. The demand and response interface process response 816 receives message 852 from this intelligent power gateway agent through the 802 power control plan interface that confirms the request for power 850.
[000162] In this illustrative example, the 808 power flow signaling process also sends the 848 information to the operations center using the 804 energy management plan interface. The 848 information serves for the integrity and state of the power circuit. virtual power.
[000163] Now, in reference to Figure 9, an illustration of an agent is shown, according to an illustrative modality. In this illustrative example, agent 900 is an example of an implementation for an agent on agents 218 in Figure 2 and / or agent 318 in Figure 3. As shown in this example, agent 900 includes the power control plan interface 902, 904 power management plan interface and 906 power flow plan interface. These interfaces can be, for example, Ethernet interfaces.
[000164] Agent 900 also includes energy management process 908, cyber security process 910, physical security process 912 and modeling / simulation interface process 914. These processes allow agent 900 to perform operations on the security plan. power management 104 in Figure 1. Furthermore, these processes, in this illustrative example, can be only a portion of the processes in agent 900.
[000165] Power management process 908 sends command and status requests 916 to a number of devices on the node associated with agent 900. Command and status requests 916 are state health information for a number of devices on the associated node to agent 900. A number of devices send 918 responses to the 908 power management process. 918 responses include the state health information requested in these examples. The 908 power management process can also receive requests for 920 commands and states from an operations center. In response to requests for commands and states 920, the power management process 908 sends status information and responses 922 to the operations center.
[000166] Cybersecurity process 910 sends cybersecurity information 924 to other agents and receives cybersecurity information 925 from other agents. 924 cybersecurity information may include logs, alerts, security events, passwords, rules, limits, policies, and / or other appropriate types of information. In addition, the cybersecurity process 910 receives requests for commands and states 926 from the operations center. The cybersecurity process 910 sends cybersecurity information 928 to the operations center. 928 cybersecurity information may include logs, alerts, security events, and / or other appropriate types of information.
[000167] Physical security process 912 sends command requests and status 930 to a number of devices on the node associated with agent 900. Physical security process 912 receives physical security information 932 from a number of devices on the node. For example, requests for 930 commands and states can be sent to a camera at the node. The camera can send the video back to 932 physical security information.
[000168] In addition, the physical security process 912 receives requests for commands and states 934 from the operations center. The physical security process 912 sends physical security information 936 to the operations center. Physical security information 936 includes logs, physical security events, alerts, and / or other appropriate information.
[000169] In these illustrative examples, the cyber security process 910 and / or physical security process 912 can be configured to receive information directly from and / or about the electric power network. For example, the physical security process 912 or cyber security process 910 can receive notification of an event that has occurred within the power grid.
[000170] In particular, the physical security process 912 can receive notification of a physical event that has occurred or is occurring within the electricity grid. In addition, the cybersecurity process 910 can receive notification of an information event, such as a message from another agent.
[000171] The cybersecurity process 910 and the physical security process 912 are configured to classify events. In addition, these processes are configured to determine whether one or more actions need to be initiated based on the classifications of these events. In some illustrative examples, these processes are configured to initiate the actions necessary to respond to these events.
[000172] The modeling / simulation interface process 914 can perform simulations for the node associated with agent 900. These simulations can be used to distribute electricity in the node.
[000173] The modeling / simulation interface process 914 receives request 938 from the operations center. Request 938 can be used for information generated by running simulations for the node. The modeling / simulation interface process 914 sends information 940 to the operations center.
[000174] In some illustrative examples, processes on agent 900 and processes on agent 800 in Figure 8 can be processes associated with the same node. For example, agent 800 and agent 900 can both run on one processor unit on one node.
[000175] The processes on agent 900 and the processes on agent 800 in Figure 8 can exchange information and / or work together to perform operations. For example, the cyber security process 910 on agent 900 can be used with the announcement process 810 on agent 800.
[000176] As a more specific example, announcement 828 can be sent from announcement process 810 on agent 800 to other agents only after cybersecurity information 924 is sent through cyber security process 910 on agent 900 to others agents. In this way, the other agents can check the node associated with agent 900 and agent 800.
[000177] Now, in reference to Figure 10, there is shown an illustration of a process to process information in an electric power network in the form of a flowchart, according to an illustrative modality. The process illustrated in Figure 10 can be implemented in the electric power environment 200 in Figure 2. In particular, this process can be implemented using one or more agents on agents 218 in Figure 2, agents 318 in Figure 3 or agents 400 in Figure 4 .
[000178] The process begins when receiving information from a number of agents in the electric power network (operation 1000). This information can be received in a number of different ways. For example, the information can comprise at least one of the sensor data, measurements, a meter reading, a voltage reading, an alert, a message, a request, a command, an image, a video, a notification, data control and other appropriate types of information.
[000179] Next, the process determines whether an event of interest occurred using the information (operation 1002). For example, in operation 1002, the process can determine whether a physical event, such as physical event 410 in Figure 4, or a cyber event, such as cyber event 412 in Figure 4, has occurred.
[000180] If an event of interest has occurred, the process classifies the event (operation 1004). The process then determines whether an action will be initiated based on the classification of the event (operation 1006). If an action is initiated, the action is identified (operation 1008). Subsequently, the action is initiated (operation 1010), with the process returning to operation 1000, as described above.
[000181] Referring again to operation 1006, if an action is not initiated, the process returns to operation 1000, as described above. Referring again to operation 1002, if an event of interest has not occurred, the process returns to operation 1000, as described above.
[000182] Referring now to Figure 11, an illustration of a flowchart of a process for classifying an event is shown, according to an illustrative modality. The process illustrated in Figure 11 can be used to implement operation 1004 in Figure 10.
[000183] The process starts when receiving an event (operation 1100). The event can be, for example, the event that was determined to have occurred in operation 1002 in Figure 10. The process then generates data for a number of parameters based on the event (operation 1102). When the event is a physical event, the parameters may include, for example, without limitation, an amount of energy, a voltage level, a current level, frequency, and / or other suitable types of parameters.
[000184] The process then determines whether the event is an expected event that uses at least one of the data for a number of parameters and a set of expected events (operation 1104). The set of expected events can be one or more events that were previously identified as expected events.
[000185] If the event is an expected event, the process determines whether the expected event is a normal event that uses at least one of the data for a number of parameters and a set of normal events (operation 1106). The set of normal events can be one or more events that were previously identified as normal events.
[000186] As used in this document, a "normal event" can be an event in which the values for the parameters that correspond to the electric power network are nominal, within the selected ones, or outside the selected limits, however, within intervals selected time frames. These parameters can include, for example, without limitation, energy level, current, voltage, frequency, power factor, and / or other suitable types of parameters. A value for a parameter that is outside the selected limits, however, within a selected time interval is a value that is outside the selected limits for a period of time below a selected limit.
[000187] An event that is not a normal event is considered an abnormal event. As used in this document, an "abnormal event" can be an event in which the values for parameters that correspond to the power grid are not nominal or are outside the selected limits and outside the selected time intervals. Furthermore, an abnormal event can be a type of emergency event. For example, an emergency type of event may be a leakage current, a short circuit, a voltage flicker, a voltage drop, an insulation break, a back-up operation, harmonic distortion, or some other suitable type of emergency type of event.
[000188] If the expected event is a normal event, then the event is classified as a normal expected event (operation 1108), with the process ending later. Otherwise, the expected event is classified as an abnormal expected event (operation 1110), with the process also ending later.
[000189] Referring again to operation 1104, if the event is not an expected event, the process determines whether the unexpected event is a normal event that uses at least one of the data for a number of parameters and the set of normal events ( operation 1112). If the unexpected event is a normal event, then the unexpected event is classified as a normal unexpected event (operation 1114), with the process also ending later. Otherwise, the process classifies the unexpected event as an abnormal unexpected event (operation 1116), with the process also ending later.
[000190] Now, with reference to Figures 12A and 12B, the illustrations of a process for classifying a switching event in the form of a flowchart are shown, according to an illustrative modality. The process illustrated in Figures 12A and 12B can be implemented in the electric power environment 200 in Figure 2. In particular, this process can be implemented in one or more agents in agents 218 in Figure 2, agents 318 in Figure 3 or agents 400 in Figure 4.
[000191] This process can be an illustrative example of how a physical event, such as switching event 414 in Figure 4, can be classified as an expected event or an unexpected event within the electrical energy environment 200. Furthermore, the process illustrated in Figures 12A and 12B can be used to implement operation 1104 in Figure 11.
[000192] The process begins with the agent that receives an identification of the switching event (operation 1200). In this illustrative example, the switching event is a connection of a load to the power grid. Certainly, in other illustrative examples, the switching event can be a disconnection of a load from the power grid or some other type of switching event.
[000193] The agent then identifies the values for a number of parameters for the switching event that uses the electricity network (operation 1202). For example, the agent can communicate with the segment of the electricity network in which the switching event occurred. This segment is a portion of the circuitry within the power grid.
[000194] The agent determines whether the type of connection formed by the switching event is a permissible connection based on the set of circuits within the segment in which the connection occurred (operation 1204). If the connection type is not an allowable connection, the process identifies the switching event as an unexpected event (1206), with the process also ending later.
[000195] Otherwise, the agent determines whether the energy consumed by the newly connected load is within the permissible limits using energy data obtained from the electricity network (operation 1208). Energy data may include, for example, energy readings from energy meters, smart meters and / or other suitable devices within and / or close to the segment of the electricity network to which the connection occurred.
[000196] If the energy consumed by the newly connected load is not within the allowable limits, the process proceeds to operation 1206, as described above. Otherwise, the agent determines whether the type of connected load is a permissible load that uses at least one of the voltage data, current data and energy factor data from the power grid (operation 1210).
[000197] If the load type is not a permissible load, the process proceeds to operation 1206, as described above. Otherwise, the agent determines whether a time-to-energy consumption ratio is within the selected limits (operation 1212). This determination can be made using, for example, without limitation, a selected period of time after the connection is formed and a level of energy consumption through the load during the selected period of time.
[000198] If the time to energy consumption ratio is not within the selected limits, the process proceeds to operation 1206, as described above. Otherwise, the agent classifies the event as an expected event (operation 1214), with the process also ending later.
[000199] Now, with reference to Figure 13, there is shown an illustration of a process to classify an energy event in the form of a flowchart, according to an illustrative modality. The process illustrated in Figure 13 can be implemented in the electric power environment 200 in Figure 2. In particular, this process can be implemented in one or more agents in agents 218 in Figure 2, agents 318 in Figure 3 or agents 400 in Figure 4 .
[000200] The process in Figure 13 can be an illustrative example of how a physical event, such as energy event 416 in Figure 4, can be classified as an expected event or an unexpected event within the electrical energy environment 200. The process illustrated in Figure 13 can be used to implement operation 1104 in Figure 11.
[000201] The process starts with the agent that receives an identification of the energy event (operation 1300). In this illustrative example, the energy event is a change in the generation of energy within the electricity grid. Certainly, in other illustrative examples, the energy event can be a change in energy demand within the electricity grid or some other type of energy event.
[000202] The agent then determines whether the amount by which the power generation has changed is permissible (operation 1302). This determination is made using, for example, without limitation, a determination as to whether the change occurs during a high season or a low season, weather information, energy data, and / or other suitable types of data.
[000203] If the amount by which the power generation has changed is not permissible, the agent classifies the energy event as an unexpected event (operation 1304), with the process also ending later. Otherwise, the agent determines whether the change in power generation affects the capacity of the electricity grid to meet the energy demand in an undesired manner (operation 1306).
[000204] If the change in power generation affects the capacity of the electric power network to meet the energy demand in an undesired manner, the process proceeds to operation 1304, as described above. Otherwise, the agent determines whether the energy that is generated corresponds to the energy that is distributed to a number of loads within selected tolerances (operation 1308).
[000205] If the energy that is generated does not correspond to the energy that is distributed to a number of loads within selected tolerances, the process proceeds to operation 1304, as described above. Otherwise, the agent determines whether the level of power quality within the power grid after the change in power generation is acceptable (operation 1310). If the power quality level is not acceptable, the process proceeds to operation 1304, as described above. Otherwise, the agent classifies the energy event as an expected event (operation 1312), with the process also ending later.
[000206] Now, with reference to Figure 14, there is shown an illustration of a process for classifying a device event in the form of a flowchart, according to an illustrative modality. The process illustrated in Figure 14 can be implemented in the electric power environment 200 in Figure 2. In particular, this process can be implemented in one or more agents in agents 218 in Figure 2, agents 318 in Figure 3 or agents 400 in Figure 4 .
[000207] The process illustrated in Figure 14 can be an illustrative example of how a physical event, such as device event 418 in Figure 4, can be classified as an expected event or an unexpected event within the electricity environment 200 The process illustrated in Figure 14 can be used to implement operation 1104 in Figure 11.
[000208] The process starts with the agent that receives an identification of a device event (operation 1400). In this illustrative example, the device event is an activation of a protective device. Certainly, in other illustrative examples, the device event can be a deactivation of a protective device or some other type of device event. The agent then determines whether a trigger event for the device event can be identified using the data from the electrical network (operation 1402).
[000209] In operation 1402, the agent can use data from the segment of the electricity network in which the device event occurred and known values for parameters for the circuitry in this segment to identify the triggering event. The triggering event can be, for example, another physical event that occurred within the power grid or a cybernetic event.
[000210] If a trigger event for the device cannot be identified, the agent determines whether the trigger event was a guideline from a main controller or operations center for the power grid (operation 1404). For example, the agent can communicate with the main controller or operations center for the power grid to make this determination.
[000211] If the trigger event was not a guideline from the main controller or operations center for the electricity network, the agent classifies the device event as an unexpected event (operation 1406), with the process also ending later . Otherwise, the agent determines whether the trigger event has been classified (operation 1408).
[000212] If the trigger event is not classified, the process proceeds to operation 1406, as described above. Otherwise, the agent determines whether a number of grounding and / or earthing elements are present at the device event site (operation 1410). This determination can be made using, for example, voltage data obtained from the electricity grid.
[000213] If the grounding and / or earthing elements are present at the device event site, the process proceeds to operation 1406, as described above. Otherwise, the agent determines whether the sides of the alternating current differ from the location where the protective device used to be connected is synchronized (operation 1412).
[000214] If the different AC sides are not synchronized, the process proceeds to operation 1406, as described above. Otherwise, the agent classifies the device event as expected (operation 1414), with the process also ending later. Referring again to operation 1402, if the trigger event can be identified, the process proceeds to operation 1408, as described above.
[000215] Now, with reference to Figure 15, there is shown an illustration of a process to classify a request in the form of a flow chart, according to an illustrative modality. The process illustrated in Figure 15 can be implemented in the electric power environment 200 in Figure 2. In particular, this process can be implemented in one or more agents in agents 218 in Figure 2, agents 318 in Figure 3 or agents 400 in Figure 4 .
[000216] The process illustrated in Figure 15 can be an illustrative example of how a cyber event, such as request 424 in Figure 4, can be classified as an expected event or an unexpected event within the electric power environment 200. The The process illustrated in Figure 15 can be used to implement operation 1104 in Figure 11.
[000217] The process begins with the agent that receives the request for information (operation 1500). The agent determines whether the request is a scheduled request for information that uses a schedule obtained through a cybersecurity process (operation 1502). If the request is not a scheduled event, the agent determines whether the request was received in response to an emergency (operation 1504). If the request was not received in response to an emergency, the agent classifies the request as an unexpected request (operation 1506), with the process also ending later.
[000218] Otherwise, the agent determines whether cybersecurity measurements have been met using the cybersecurity process (operation 1508). This determination can be made by assessing the integrity of the request using the cybersecurity process.
[000219] If cybersecurity measurements have not been met, the process proceeds to operation 1506, as described above. Otherwise, the agent determines whether the information that is requested is obtainable (operation 1510). In operation 1510, the agent makes this determination using the cybersecurity process to evaluate the content of the request. The agent determines whether the information requested is recorded or measured.
[000220] If the information that is requested is not obtainable, the process proceeds to operation 1506, as described above. Otherwise, the agent determines whether the information that is requested can be sent based on security rules (operation 1512). For example, in operation 1512, the agent determines whether sending information to the request can violate one or more security rules or share rules established by the cybersecurity process.
[000221] If the information that is requested cannot be sent based on security rules, the process proceeds to operation 1506, as described above. Otherwise, the agent classifies the request as an expected request (operation 1514), with the process also ending later. Referring again to operation 1502, if the request is for a scheduled event, the process proceeds to operation 1508, as described above.
[000222] Now, with reference to Figure 16, there is shown an illustration of a process for classifying a command, according to an illustrative modality. The process illustrated in Figure 16 can be implemented in the electric power environment 200 in Figure 2. In particular, this process can be implemented in one or more agents in agents 218 in Figure 2, agents 318 in Figure 3 or agents 400 in Figure 4 .
[000223] The process illustrated in Figure 16 can be an illustrative example of how a cybernetic event, such as command 422 in Figure 4, can be classified as an expected event or an unexpected event within the 200 power environment. The process illustrated in Figure 16 can be used to implement operation 1104 in Figure 11.
[000224] The process starts with the agent that receives a command that requests an action to be performed (operation 1600). The agent determines whether the command is a programmed command using programming obtained through a cybersecurity process (operation 1602). If the command is not a scheduled event, the agent determines whether the command was received in response to an emergency (operation 1604). If the command was not received in response to an emergency, the agent classifies the command as an unexpected request (operation 1606), with the process also ending later.
[000225] Otherwise, the agent determines whether cybersecurity measurements have been met using the cybersecurity process (operation 1608). This determination can be made by assessing the integrity of the command using the cybersecurity process.
[000226] If cybersecurity measurements have not been met, the process proceeds to operation 1606, as described above. Otherwise, the agent determines whether the action requested by the command is permissible (operation 1610). In operation 1610, the agent makes this determination using the cybersecurity process, for example, to assess the security rules established by the cybersecurity process.
[000227] If the requested action is not permissible, the process proceeds to operation 1606, as described above. Otherwise, the agent determines whether the command was received in response to an action that is identifiable using the cybersecurity process (operation 1612). This determination can be made using the cybersecurity process to evaluate the content of the command. For example, the agent determines whether the command is the result of an action that can be defined or measured in some way.
[000228] If the command was not received in response to an action that is identifiable, the agent determines whether the command is predictable based on the state of the electricity network (operation 1614). If the command is not predictable, the agent determines whether the command is a simulated command (operation 1616). As used in this document, a "simulated command" can be a command that has been generated to simulate an actual command. The simulated command can be generated for the purposes of testing the power grid.
[000229] If the command is a simulated command, the agent identifies the command as an expected event (operation 1618), with the process also ending later. Otherwise, the process proceeds to operation 1606, as described above.
[000230] Referring again to operation 1614, if the command is predictable, the process proceeds to operation 1618. Referring again to operation 1612, if the command was received in response to an action that is identifiable, the process proceeds until operation 1618, as described above. Furthermore, referring again to operation 1602, if the command is a programmed command, the process proceeds to operation 1608, as described above.
[000231] Now, in reference to Figure 17, an illustration of a process to respond to a physical event is shown based on a classification of the event in the form of a flowchart, according to an illustrative modality. The process illustrated in Figure 17 can be used to implement operation 1004 and operation 1006 in Figure 10.
[000232] The process illustrated in Figure 17 can be implemented in the electric power environment 200 in Figure 2. In particular, this process can be implemented in one or more agents in agents 218 in Figure 2, agents 318 in Figure 3 or agents 400 in Figure 4. In particular, the process illustrated in Figure 17 can be implemented using, for example, without limitation, the classifier 402 and / or analyzer 404 on agent 400 in Figure 4.
[000233] The process begins with the agent that determines whether the event is classified as a normal expected event, an abnormal expected event, a normal unexpected event or an abnormal unexpected event (operation 1700). If the event is classified as a normal expected event, the agent determines that no further action is required (operation 1702), with the process also ending later.
[000234] If the event is classified as an expected abnormal event, the agent identifies and performs an action indicated by an electrical standard (operation 1704). The electrical standard used can be, for example, the National Electrical Code (NEC).
[000235] Referring again to operation 1700, if the event is classified as a normal unexpected event, the agent identifies a number of parameters for the event that are outside the limits selected for the number of parameters (operation 1706). Thereafter, the agent monitors the number of parameters for a selected period of time (operation 1708). For example, in operation 1708, the agent can monitor total energy consumption, meter readings and / or other types of data to monitor these parameters. The agent then determines whether an inconsistency has been detected (operation 1710). The inconsistency may be some unwanted occurrence within the power grid.
[000236] If an inconsistency was not detected, the agent reclassifies the event as an expected event (operation 1712), with the process also ending later. In these illustrative examples, classifier 402 at agent 400 can receive this reclassification of the event and begin further reclassification of the event in operation 1106 in Figure 11.
[000237] Referring again to operation 1710, if an inconsistency is detected, the process determines whether an event source is an authorized event (operation 1714). The origin of the event can be, for example, a command that resulted in the event, a message that resulted in the event, a natural physical event, or some other suitable type of origin for the event. For example, a message can cause an action that results in the event. In operation 1714, the agent can use the control data received from a main control agent for the electricity network, data from an operations center, and / or other data suitable for making the determination.
[000238] If the origin of the event is authorized, the process proceeds to operation 1712, as described above. Otherwise, the process proceeds to operation 1716 described below. Referring again to operation 1700, if the event is classified as an unexpected abnormal event, the agent locates and isolates a portion of the electric power network in which the event occurred or is occurring (operation 1716). This portion of the electricity grid can be referred to, for example, as an affected segment of the electricity grid. Isolating this portion of the electrical power network may include interrupting a flow of energy in this area.
[000239] The agent then identifies a number of actions to be initiated based on the event (operation 1718). In operation 1718, the number of actions may include, for example, without limitation, contacting a number of customers, contacting a manager, generating a number of alerts, dispatching a team, initiating a cyber security process, redistribute energy to the affected area if diversion is allowed and / or other suitable types of actions. The agent can then initiate a number of identified actions (operation 1720), with the process also ending later.
[000240] Now, with reference to Figure 18, an illustration is shown of a process for responding to a command based on a classification of the command in the form of a flowchart, according to an illustrative modality. The process illustrated in Figure 18 can be used to implement operation 1004 and operation 1006 in Figure 10.
[000241] The process illustrated in Figure 18 can be implemented in the electric power environment 200 in Figure 2. In particular, this process can be implemented in one or more agents in agents 218 in Figure 2, agents 318 in Figure 3 or agents 400 in Figure 4.
[000242] The process begins with the agent that determines whether the command is classified as a normal expected event, an abnormal expected event, a normal unexpected event or an abnormal unexpected event (operation 1800). If the command is classified as a normal expected event, the agent initiates the action requested by the command (operation 1802), with the process also ending later.
[000243] If the command is classified as an expected abnormal event, the agent determines whether a command source is authorized (operation 1804). If the origin of the command is authorized, the agent marks the classification of the command as an error and reevaluates the command (operation 1806). In these illustrative examples, the reevaluation of the command can be performed using the classifier 402 and / or analyzer 404 on agent 400 in Figure 4.
[000244] In particular, the command will still be considered an expected command, however, the command is reevaluated to determine whether the command is normal or abnormal. In operation 1806, the reevaluation can be carried out to analyze the state of the electricity network and determine how the action requested by the command will affect the electricity network.
[000245] The agent then determines whether the command is normal (operation 1808). If the command is normal, the process proceeds to operation 1802, as described above. Otherwise, the agent initiates a cybersecurity process (operation 1810), with the process also ending later. The cybersecurity process can be initiated to protect the power grid.
[000246] Referring again to operation 1804, if the origin of the command is not authorized, the process proceeds to operation 1810. Furthermore, referring again to operation 1800, if the command is classified as an unexpected normal event, the agent determines whether a command source is authorized (operation 1812).
[000247] If the origin of the command is not authorized, the process proceeds to operation 1810. Otherwise, the agent reevaluates the command (operation 1814). In particular, the command is still considered a normal command, however, the command is reevaluated to determine whether the command is expected or unexpected based on a state of the power grid and the action that is requested by the command.
[000248] The agent then determines whether the command is expected (operation 1816). If the command is expected, the process proceeds to operation 1802, as described above. Otherwise, the process proceeds to operation 1804, as described above.
[000249] Referring again to operation 1800, if the command is classified as an unexpected abnormal event, the agent isolates the command (operation 1818). The agent then identifies a number of actions to be taken based on the origin of the command and / or the action that is requested by the command (operation 1820). In some illustrative examples, carrying out operation 1810 can be considered one of the actions that can be taken. The agent then starts a number of identified actions (operation 1822), with the process also ending later.
[000250] Now, in reference to Figure 19, an illustration is shown of a process for responding to a request based on a classification of the request in the form of a flowchart, according to an illustrative modality. The process illustrated in Figure 19 can be used to implement operation 1004 and operation 1006 in Figure 10.
[000251] The process illustrated in Figure 19 can be implemented in the electric power environment 200 in Figure 2. In particular, this process can be implemented in one or more agents in agents 218 in Figure 2, agents 318 in Figure 3 or agents 400 in Figure 4. In particular, the process illustrated in Figure 19 can be implemented using, for example, without limitation, the classifier 402 and / or analyzer 404 on agent 400 in Figure 4.
[000252] The process begins with the agent that determines whether the request is classified as a normal expected event, an abnormal expected event, a normal unexpected event, or an unexpected unexpected event (operation 1900). The request can be a request for information.
[000253] Furthermore, the request can be classified as a normal expected event when the request is a scheduled and / or approved request. The request can be classified as an expected abnormal event when the request is not a scheduled request, but it is a type of request that can be received in an emergency situation. In addition, the request can be classified as a normal unexpected event when the request is not a request during an emergency. The request can be classified as an unexpected abnormal event when the request is neither scheduled nor received during an emergency.
[000254] If the request is classified as a normal expected event, the agent proceeds with providing the information that is requested (operation 1902), with the process also ending later. If the request is classified as an expected abnormal event, the process determines whether any portion of the power grid is a state of emergency (operation 1904). This portion may be, for example, one or more segments of the electricity network. The agent can use, for example, sensor data and / or other types of data from the electricity grid to make this determination.
[000255] If any portion of the electricity network is in a state of emergency, the process proceeds to operation 1902, as described above. Otherwise, the agent proceeds to operation 1906, as described below. Referring again to operation 1900, if the request is classified as a normal unexpected event, the agent determines whether an origin of the request is authorized (operation 1906).
[000256] If the agent determines that the origin of the request is authorized, the agent determines whether the request was sent in error based on a state of the origin (operation 1908). In operation 1908, the agent checks the state of the origin. For example, the process can use sensor data from a device on the power grid that sent the request to determine whether the device has been compromised, is operating within the selected limits, or is operating in some other way.
[000257] If the request was not sent in error, the agent reclassifies the request as a normal expected event (operation 1910) and then proceeds to operation 1902, as described above. Referring again to operation 1908, if the request was sent in error, the agent abandons the message (operation 1912), with the process also ending later. In operation 1912, the agent does not provide the information that is requested. In some cases, in operation 1912, the agent sends the request to classifier 402 at agent 400 for reassessment.
[000258] Referring again to operation 1900, if the request is classified as an unexpected abnormal event, the agent isolates the request and initiates a cyber security process (operation 1914), with the process also ending later. Referring again to operation 1906, if the agent determines that the origin of the request is not authorized, the process proceeds to operation 1914, as described above.
[000259] Flowcharts, process flows and block diagrams in the different modalities shown illustrate the architecture, functionality and operation of some possible implementations of the device and methods in an illustrative modality. In this regard, each block in flowcharts, process flows or block diagrams can represent a module, segment, function and / or a portion of an operation or step. For example, one or more of the blocks can be implemented as program code, in hardware, or a combination of program code and hardware. When implemented in hardware, the hardware can, for example, take the form of integrated circuits that are manufactured or configured to perform one or more operations in flowcharts or block diagrams.
[000260] In some alternative implementations of an illustrative modality, the function or functions noted in the blocks may occur outside the order noted in the Figures. For example, in some cases, two blocks shown in succession can be executed substantially simultaneously, or the blocks can sometimes be performed in reverse order, depending on the functionality involved. Also, other blocks can be added in addition to the blocks illustrated in a flowchart or block diagram.
[000261] Referring now to Figure 20, there is shown an illustration of a data processing system in the form of a block diagram, according to an illustrative modality. In this illustrative example, data processing system 2000 can be used to implement a data processing system in data processing systems 216 in Figure 2 and / or processor unit 310 in Figure 3.
[000262] Furthermore, the 2000 data processing system can be used to implement an agent, according to an illustrative modality. For example, data processing system 2000 can be used to deploy an agent to agents 218 in Figure 2, agent 318 in Figure 3, and / or agent 400 in Figure 4. In this illustrative example, data processing system 2000 includes communications structure 2002, which provides communications between processor unit 2004, memory 2006, persistent storage 2008, communications unit 2010, input / output (I / O) unit 2012 and screen 2014.
[000263] The processor unit 2004 is used to execute instructions for software that can be loaded into the 2006 memory. The processor unit 2004 can be a number of processors, a multiprocessor core, or some other type of processor, depending on the particular implementation. As used herein, in reference to an item, a number means one or more items. In addition, processor unit 2004 can be implemented using a number of heterogeneous processor systems in which a main processor is present with secondary processors on a single chip. As another illustrative example, processor unit 2004 can be a symmetric multiprocessor system containing multiple processors of the same type.
[000264] Memory 2006 and persistent storage 2008 are examples of storage devices 2016. A storage device consists of any piece of hardware that is capable of storing information, such as, for example, without limitation, data, program code in functional form, and / or other appropriate information on a temporary basis and / or a permanent basis. 2016 storage devices can also be referred to as computer-readable storage devices in these examples. The 2006 memory in these examples can be, for example, a random access memory or any other suitable volatile or non-volatile storage device. Persistent storage 2008 can take many forms, depending on the particular implementation.
[000265] For example, persistent storage 2008 can contain one or more components or devices. For example, persistent storage 2008 can be a hard drive, a flash memory, a rewritable optical disc, a rewritable magnetic tape or some combination above. The medium used by persistent storage 2008 can also be removable. For example, a removable hard drive can be used for persistent storage 2008.
[000266] The communications unit 2010, in these examples, provides communications with other data processing systems or devices. In these examples, the communications unit 2010 is a network interface card. The communications unit 2010 can provide communications through the use of both physical and wireless communications links.
[000267] The input / output unit 2012 allows data input and output with other devices that can be connected to the 2000 data processing system. For example, the input / output unit 2012 can provide a connection for user input through a keyboard, a mouse and / or add some other suitable input device. In addition, the 2012 input / output unit can send the output to a printer. The 2014 screen provides a mechanism for displaying information to a user.
[000268] Instructions for the operating system, applications and / or programs can be found on the 2016 storage devices, which are in communication with the processor unit 2004 through the 2002 communications structure. In these illustrative examples, the instructions are found in a functional form in persistent storage 2008. These instructions can be loaded into memory 2006 for execution through processor unit 2004. Processes of the different modes can be performed by processor unit 2004 using computer-implemented instructions, which can be found at a memory, such as the 2006 memory.
[000269] These instructions are referred to as program code, computer-usable program code or computer-readable program code that can be read and executed by a processor in the processor unit 2004. The program code in different modes can be incorporated on different computer-readable or physical storage media, such as memory 2006 or persistent storage 2008.
[000270] The program code 2018 is located in a functional form on the 2020 computer-readable media that is selectively removable and can be loaded or transferred to the 2000 data processing system for execution through the 2004 processor unit. program 2018 and computer-readable media 2020 form the product of computer program 2022 in these examples. In one example, the computer-readable media 2020 could be the computer-readable storage media 2024 or the computer-readable signal media 2026.
[000271] The 2024 computer-readable storage media may include, for example, an optical or magnetic disk that is inserted or placed in a drive or other device that is part of the persistent storage 2008 for transfer over a storage device, such as , a hard drive, which is part of persistent storage 2008. The 2024 computer-readable storage media can also take the form of persistent storage, such as a hard drive, a flash drive or a flash memory, which is connected to the 2000 data processing system. In some instances, the 2024 computer-readable storage media may not be removable from the 2000 data processing system.
[000272] In these examples, computer-readable storage media 2024 is a physical or tangible storage device used to store program code 2018 instead of a medium that propagates or transmits program code 2018. Storage media readable by computer 2024 is also referred to as a tangible computer-readable storage device or a physical computer-readable storage device. In other words, the 2024 computer-readable storage medium is a medium that can be touched by a person.
[000273] Alternatively, program code 2018 can be transferred to data processing system 2000 using computer-readable signal media 2026. Computer-readable signal media 2026 can be, for example, a code program containing propagated data signal 2018. For example, the 2026 computer-readable signal medium may be an electromagnetic signal, an optical signal and / or any other suitable type of signal. These signals can be transmitted via communications links, such as wireless communications links, fiber optic cable, coaxial cable, a wire and / or any other suitable type of communications link. In other words, the communications link and / or the connection can be physical or wireless in the illustrative examples.
[000274] In some illustrative embodiments, the program code 2018 can be downloaded over the network to persistent storage 2008 from another device or data processing system via the computer-readable signal media 2026 for use within the 2000 data processing system. For example, program code stored on a computer-readable storage medium on a server data processing system can be downloaded over a network from the server to the processing system 2000 data system. The data processing system that provides the 2018 program code can be a server computer, a client computer or some other device capable of storing and transmitting the 2018 program code.
[000275] The different components illustrated for the 2000 data processing system are not intended to provide architectural limitations to the way in which the different modalities can be implemented. The different illustrative modalities can be implemented in a data processing system that includes components in addition to or in place of those illustrated for the 2000 data processing system. Other components shown in Figure 20 can be varied from the illustrative examples shown. The different modalities can be implemented using any device or hardware system capable of executing program code. As an example, the data processing system can include organic components integrated with inorganic components and / or can be fully understood by organic components that exclude a human being. For example, a storage device can be comprised of an organic semiconductor.
[000276] In another illustrative example, the processor unit 2004 can take the form of a hardware unit that has circuits that are manufactured or configured for a particular use. This type of hardware can perform operations without requiring the program code to be loaded into memory from a storage device to be configured to perform the operations.
[000277] For example, when the processor unit 2004 takes the form of a hardware unit, the processor unit 2004 can be a circuit system, an application specific integrated circuit (ASIC), a programmable logic device, or some another suitable type of hardware configured to perform a number of operations. With a programmable logic device, the device is configured to perform a number of operations. The device can be reconfigured at a later time or it can be permanently configured to perform a number of operations. Examples of programmable logic devices include, for example, a programmable logic matrix, a field programmable logic matrix, a field programmable port arrangement, and other suitable hardware devices. With this type of implementation, the program code 2018 can be omitted, because the process for the different modalities are implemented in a hardware unit.
[000278] In yet another illustrative example, processor unit 2004 can be implemented using a combination of processors found in computers and hardware units. Processor unit 2004 can have a number of hardware units and a number of processors that are configured to run the 2018 program code. With this example shown, some of the processes can be implemented on a number of hardware units, while others processes can be implemented on a number of processors.
[000279] In another example, a bus system can be used to implement the 2002 communications structure and can be comprised of one or more buses, such as a system bus or an input / output bus. Certainly, the bus system can be implemented using any suitable type of architecture that provides a transfer of data between different components or devices attached to the bus system.
[000280] In addition, a communications unit may include a number of devices that transmit data, receive data or transmit and receive data. A communications unit can be, for example, a modem or a network adapter, two network adapters, or some combination of these. In addition, a memory can be, for example, the 2006 memory or a cache, such as, found in a memory controller interface and hub that can be present in the 2002 communications structure.
[000281] In the text and Figures, in one aspect, an apparatus includes: an agent 400 configured to receive information 406 from an electrical power network 202, identify an event 408 from information 406, classify event 408, determine whether to initiate an action based on an event 408 classification and initiate the action in response to a determination to initiate action. In a variant, the device on which, when being configured to initiate action in response to the determination to initiate action, agent 400 is configured to identify the action and initiate the action identified in response to the determination to initiate action. In another variant, the device includes event 408 which is classified as one of a normal expected event 430, an abnormal expected event 432, a normal unexpected event 434 and an unexpected abnormal event 436. In yet another variant, the device on which the Agent 400 is configured to determine whether to initiate action in response to event 408 and is classified as the unexpected abnormal event 436.
[000282] In one example, the device on which when being configured to classify event 408, agent 400 is configured to determine whether a message 420 that causes another action that results in event 408 is an expected message 420, to determine whether the event 408 is a normal event 408 and classify event 408 based on whether message 420 is expected message 420 and whether event is normal event 408. In another example, the device on which agent 400 is additionally configured to identify a message 420 in information 406 where message 420 is a cause of event 408 and when being configured to determine whether to initiate the action based on the classification of event 408, agent 400 is configured to determine whether to initiate the action based on the classification of event 408 and based on a source of message 420, where message 420 is selected from one between a command 422 and a request 424. In yet another example, the device on which the agent 400 is configur to determine that action is required when event 408 is classified as an unexpected abnormal event 436 and message 420 originates from outside the electrical power network 202.
[000283] In one example, the device in which agent 400 includes a classifier 402 configured to receive information 406 from the electrical network 202, identify event 408 from the information and classify the event and a configured analyzer 404 to determine whether to initiate action based on the event 408 classification and initiate action in response to the determination to initiate action.
[000284] In another example, the device additionally includes: a node in the electrical power network 202, in which agent 400 is associated with the node.
[000285] In yet another example, the apparatus additionally includes: a number of lines 233 in the electrical power network 202, in which the number of lines 233 is configured to transmit electrical energy 214; a plurality of nodes 224 in the electrical power network 202, wherein the plurality of nodes 224 is configured to control electrical energy 214 carried on a number of lines 233; a communications network 204 configured to transmit information 406; and a number of agents 226 associated with the plurality of nodes 224, wherein a number of agents 226 are configured to communicate with each other using communications network 204, configuring the plurality of nodes 224 on the electrical power network 202 in a circuit, controlling a distribution of electrical energy 214 through the circuit for a number of loads associated with the circuit and generating messages 824.
[000286] In one aspect, an apparatus is described that includes a plurality of nodes 224 in an electrical power network 202, wherein the plurality of nodes 224 is configured to control electrical energy 214 transmitted over a number of lines 233 in the electric power network 202; a communications network 204 configured to transmit information 406; and a number of agents 226 associated with the plurality of nodes 224, where a number of agents 226 are configured to send information to each other using communications network 204 and where an agent 400 among a number of agents 226 is configured to receive the information 406 from the electricity grid 202, identify an event from information 406, classify event 408, determine whether to initiate an action based on a classification of event 408 and initiate action in response to a determination to start the action.
[000287] In a variant, the device in which, when being configured to initiate the action in response to the determination to initiate the action, agent 400 is configured to identify the action to initiate the action identified in response to the determination to initiate the action. In another variant, the device on which event 408 is classified as one of a normal expected event 430, an abnormal expected event 432, a normal unexpected event 434 and an unexpected abnormal event 436 and where agent 400 is configured to start the action in response to event 408 which is classified as the unexpected abnormal event 436. In yet another variant, the device on which agent 400 is additionally configured to identify a message 420 in information 406 where message 420 is a cause of event 408 and where when being configured to determine whether to initiate the action based on the classification of event 408, agent 400 is configured to determine whether to initiate the action based on the classification of event 408 and based on a source message 420.
[000288] In one example, the device on which agent 400 is configured to determine that action is required when event 408 is classified as an unexpected abnormal event 436 and message 420 originates from outside the power grid 202. In another example, the device on which the agent includes a classifier 402 configured to receive information 406 from the electrical network 202, identify the event from information 406 and classify event 408 and an analyzer 404 configured to determine whether to initiate action based on the event 408 classification and initiate action in response to the determination to initiate action.
[000289] In one aspect, a method for processing information on an electrical power network 202 is described, the method includes: receiving information 406 from a number of agents 226 on the electrical power network 202; identify an event 408 from information 406; classify event 408; determine whether to initiate an action based on a classification of event 408; and initiate action in response to a determination to initiate action. In a variant, the method includes initiating the action in response to the determination to initiate the action which includes identifying the action; and
[000290] initiate the action identified in response to the determination to initiate the action. In yet another variant, the method in which event 408 is classified as one among a normal expected event 408, an abnormal expected event 432, a normal unexpected event 434 and an unexpected unexpected event 436.
[000291] In yet another, the method additionally includes: identifying a message 420 in information 406 in which message 420 is a cause of event 408 and in which to determine whether to initiate the action based on the classification of event 408 comprises: determine whether to initiate the action based on the classification of event 408 and based on a source of message 420, where message 420 is selected from one between a command 422 and a request 424.
[000292] The description of the different illustrative modalities has been presented for purposes of illustration and the description is not intended to be exhaustive or limited to the modalities in the manner described. Many modifications and variations will be apparent to those of ordinary skill in the art. In addition, different illustrative modalities can provide different resources when compared to other desired modalities. The selected modality or modalities are chosen and described in order to better explain the principles of the modalities, the practical application and to allow others with common knowledge in the technique to understand the description for different modalities with the various modifications, as they are suitable for the particular use contemplated.

权利要求:
Claims (9)
[0001]
1. Apparatus comprising: an agent (400), which comprises a computer-readable medium, configured to receive information (406) from an electric power network (202), identify an event (408) from the information ( 406), classify the event (408), determine whether to initiate an action based on an event classification (408), initiate the action in response to a determination to initiate the action, the apparatus characterized by the fact that the agent is further configured to: determine if a message (420) that causes another action that results in the event (408) is an expected message (420), determine if the event (408) is a normal event (408), and classify the event (408) based on whether the message (420) is the expected message (420) and whether the event is the normal event (408).
[0002]
2. Apparatus, according to claim 1, characterized by the fact that it is configured to initiate the action in response to the determination to initiate the action, the agent (400) is configured to identify the action and initiate the action identified in response to the determination to initiate action.
[0003]
3. Apparatus according to claim 1 or 2, characterized by the fact that the event (408) is classified as one among a normal expected event (430), an abnormal expected event (432), a normal unexpected event ( 434) and an unexpected abnormal event (436), where the agent is configured to determine whether to initiate action in response to the event (408) which is classified as the unexpected abnormal event (436).
[0004]
4. Apparatus according to claim 3, characterized by the fact that the agent (400) is further configured to identify a message (420) in the information (406) in which the message (420) is a cause of the event (408 ), and when being configured to determine whether to initiate action based on event classification (408), agent (400) is configured to determine whether to initiate action based on event classification (408 ) and based on a message source (420), where the message (420) is selected from a command (422) and a request (424); and where the agent (400) is configured to determine that the action is necessary when the event (408) is classified as an unexpected abnormal event (436) and the message (420) originates from outside the power grid (202).
[0005]
Apparatus according to any one of claims 1 to 4, characterized by the fact that it further comprises: a node in the electrical power network (202), in which the agent (400) is associated with the node; a number of lines (233) in the electrical power network (202), wherein a number of lines (233) are configured to transmit electrical energy (214); a plurality of nodes (224) in the electrical power network (202), wherein the plurality of nodes (224) is configured to control the electrical energy (214) transmitted in the number of lines (233); a communications network (204) configured to transmit information (406); and a number of agents (226) associated with the plurality of nodes (224), in which the number of agents (226) is configured to communicate with each other using the communications network (204), configure the plurality of nodes (224) in the electric power network (202) in a circuit, control a distribution of electric power (214) through the circuit for a number of loads associated with the circuit and generate the messages (824); and wherein the agent (400) includes a classifier (402) configured to receive information (406) from the electricity network (202), identify event (408) of the information, and classify the event, and an analyzer (404) configured to determine whether to initiate action based on event classification (408) and initiate action in response to the determination to initiate action.
[0006]
6. Apparatus according to any one of claims 1 to 5, characterized by the fact that it comprises: a plurality of nodes (224) in an electric power network (202), in which the plurality of nodes (224) is configured to control electrical energy (214) transmitted over a number of lines (233) in the electrical network (202); a communications network (204) configured to transmit information (406); and a number of agents (226) associated with the plurality of nodes (224), in which the number of agents (226) is configured to send the information to each other using the communications network (204) and in which the agent ( 400) the number of agents (226) is configured to receive information from the electric power network, identify an event from the information, classify the event, determine whether to start the action based on an event classification, and start action in response to a determination to initiate action.
[0007]
7. Apparatus according to claim 6, characterized by the fact that when being configured to initiate the action in response to the determination to initiate the action, the agent (400) is configured to identify the action and initiate the action identified in response the determination to initiate action; where event (408) is classified as one of a normal expected event (430), an abnormal expected event (432), a normal unexpected event (434) and an abnormal unexpected event (436), and where the agent ( 400) is configured to initiate the action in response to the event (408) which is classified as the unexpected abnormal event (436); and where the agent (400) is further configured to identify a message (420) in the information (406) where the message (420) is a cause of the event (408) and when being configured to determine whether to initiate if the action is based on the event classification (408), the agent (400) is configured to determine whether to initiate the action based on the event classification (408) and based on a message source (420).
[0008]
8. Method for processing information in an electric power network (202), the method which comprises: receiving information (406) from a number of agents (226) in the electric power network (202); identify an event (408) from the information (406); classify the event (408); determine whether to initiate an action based on an event classification (408); initiate action in response to a determination to initiate action; the method being characterized by the steps of: determining whether a message (420) that causes another action that results in the event (408) is an expected message (420), determining whether the event (408) is a normal event (408), and classifying the event (408) based on whether the message (420) is the expected message (420) and whether the event is the normal event (408); where the method additionally comprises identifying a message (420) in the information (406) where the message (420) is a cause of the event (408) and where determining whether to initiate action based on the classification of the event (408) comprises: determining whether to initiate the action based on the classification of the event (408) and based on a message source (420), in which the message (420) is selected from one of a command (422) and a request (424).
[0009]
9. Method, according to claim 8, characterized by the fact that initiating the action in response to the determination to initiate the action comprises: identifying the action; and initiate the action identified in response to the determination to initiate the action; and in which event (408) is classified as one among a normal expected event (408), an abnormal expected event (432), a normal unexpected event (434) and an abnormal unexpected event (436).

类似技术:

---

公开号 | 公开日 | 专利标题

---

BR102013008143B1|2020-10-20|apparatus and method for processing information in an electric power network

---

USRE48073E1|2020-06-30|Methods of deploying a server

---

Davis et al.2015|A cyber-physical modeling and assessment framework for power grid infrastructures

---

CN103229481B|2015-01-21|Networking devices for monitoring utility usage and methods of using same

---

CN103107960B|2016-08-17|The method and system of the impact of exchange trouble in switching fabric is reduced by switch card

---

CN110036600A|2019-07-19|The convergence service of network health data

---

BR102013015753B1|2020-12-29|method for monitoring the operation of an electric power system; and monitoring system

---

EA016898B1|2012-08-30|Policy-based networking utility service

---

US9245147B1|2016-01-26|State machine reference monitor for information system security

---

Cetinay et al.2018|Nodal vulnerability to targeted attacks in power grids

---

Venkataramanan et al.2019|CP-SAM: Cyber-physical security assessment metric for monitoring microgrid resiliency

---

CN110036599A|2019-07-19|The programming interface of network health information

---

Sándor et al.2019|Cyber attack detection and mitigation: Software defined survivable industrial control systems

---

Rygielski et al.2013|Model-based throughput prediction in data center networks

---

CN103605560A|2014-02-26|Cascading failure parallel simulation method for relay protection and safety automata

---

Dorsch et al.2018|Enabling hard service guarantees in software-defined smart grid infrastructures

---

Kang et al.2020|An automatic algorithm of identifying vulnerable spots of internet data center power systems based on reinforcement learning

---

Meza et al.2015|Quantifying observability in state estimation considering network infrastructure failures

---

Marchetto et al.2020|A formal approach to verify connectivity and optimize VNF placement in industrial networks

---

CN105450751A|2016-03-30|System capable of improving stability of cloud computing environment

---

Dong et al.2021|Modeling and vulnerability analysis of spatially embedded heterogeneous cyber-physical systems with functional dependency

---

Ebrahimy2014|Investigating SCADA failures in interdependent critical infrastructure systems

---

Qu et al.2020|Dynamic Data-Driven Self-healing Application for Phasor Measurement Unit Networks

---

KR102235150B1|2021-04-02|Smart grid network system by using software defined networking technology and its operation method

---

Cantero-Gubert et al.2020|Building a testing environment for SDN networks analysis for electrical grid applications

同族专利:

---

公开号 | 公开日

---

EP2651098A1|2013-10-16|

---

US9020652B2|2015-04-28|

---

BR102013008143A2|2015-06-16|

---

US20130274941A1|2013-10-17|

---

JP2013226037A|2013-10-31|

---

EP2651098B1|2018-12-05|

---

JP6212276B2|2017-10-11|

引用文献:

---

公开号 | 申请日 | 公开日 | 申请人 | 专利标题

---

---

US7216043B2|1997-02-12|2007-05-08|Power Measurement Ltd.|Push communications architecture for intelligent electronic devices|

---

CN101309168A|2000-07-31|2008-11-19|株式会社东芝|Agent system|

---

JP2003050842A|2001-08-06|2003-02-21|Toshiba Corp|Protection/control device and protection/control system for power system|

---

US7665119B2|2004-09-03|2010-02-16|Secure Elements, Inc.|Policy-based selection of remediation|

---

US9282001B2|2007-03-05|2016-03-08|Grid Net, Inc.|Policy based utility networking|

---

US8806239B2|2007-08-28|2014-08-12|Causam Energy, Inc.|System, method, and apparatus for actively managing consumption of electric power supplied by one or more electric power grid operators|

---

US8863278B2|2008-05-28|2014-10-14|International Business Machines Corporation|Grid security intrusion detection configuration mechanism|

---

US8181251B2|2008-12-18|2012-05-15|Symantec Corporation|Methods and systems for detecting malware|

---

WO2010141375A2|2009-06-01|2010-12-09|Phatak Dhananjay S|System, method, and apparata for secure communications using an electrical grid network|

---

JP2011154410A|2010-01-25|2011-08-11|Sony Corp|Analysis server and method of analyzing data|

---

US8655499B2|2010-02-19|2014-02-18|The Boeing Company|Controlling virtual power circuits|

---

US8315743B2|2010-02-19|2012-11-20|The Boeing Company|Network centric power flow control|

---

US8712596B2|2010-05-20|2014-04-29|Accenture Global Services Limited|Malicious attack detection and analysis|

---

US20130247205A1|2010-07-14|2013-09-19|Mcafee, Inc.|Calculating quantitative asset risk|

---

US8566936B2|2011-11-29|2013-10-22|Radware, Ltd.|Multi dimensional attack decision system and method thereof|

---

US8595845B2|2012-01-19|2013-11-26|Mcafee, Inc.|Calculating quantitative asset risk|

---

US9203859B2|2012-02-01|2015-12-01|The Boeing Company|Methods and systems for cyber-physical security modeling, simulation and architecture for the smart grid|US20140129042A1|2012-11-07|2014-05-08|Dorazio Enterprises, Inc.|Community Based Energy Management System|

---

EP2806521A1|2013-05-22|2014-11-26|Vito NV|System for electricity grids for adjusting or matching the electrical demand|

---

CN103677212A|2013-12-12|2014-03-26|中南林业科技大学|Method for low-power-consumption real-time data processing based on CPS|

---

US9954362B2|2014-05-23|2018-04-24|California Institute Of Technology|Systems and methods for optimal power flow on a radial network|

---

US10673232B2|2014-07-10|2020-06-02|California Institute Of Technology|Dynamic frequency control in power networks|

---

WO2016022603A1|2014-08-04|2016-02-11|California Institute Of Technology|Distributed gradient descent for solving optimal power flow in radial networks|

---

US10063280B2|2014-09-17|2018-08-28|At&T Intellectual Property I, L.P.|Monitoring and mitigating conditions in a communication network|

---

US10365676B2|2015-04-30|2019-07-30|Abb Inc.|Secured control of circuit breakers in a digital substation|

---

US9912027B2|2015-07-23|2018-03-06|At&T Intellectual Property I, L.P.|Method and apparatus for exchanging communication signals|

---

US10079486B2|2015-12-03|2018-09-18|Abb Inc.|Securing against malicious control of circuit breakers in electrical substations|

---

WO2017147612A1|2016-02-25|2017-08-31|California Institute Of Technology|Adaptive charging network using adaptive charging stations for electric vehicles|

---

US10811767B2|2016-10-21|2020-10-20|At&T Intellectual Property I, L.P.|System and dielectric antenna with convex dielectric radome|

---

US10476902B2|2017-04-26|2019-11-12|General Electric Company|Threat detection for a fleet of industrial assets|

---

EP3718073A4|2017-12-01|2021-08-25|California Institute of Technology|Optimization framework and methods for adaptive ev charging|

---

CN111400890B|2020-03-11|2021-01-05|湖南大学|Attack-defense structure-based power grid upgrading method for resisting malicious data attack|

法律状态:
2015-06-16| B03A| Publication of a patent application or of a certificate of addition of invention [chapter 3.1 patent gazette]|

---

2018-12-04| B06F| Objections, documents and/or translations needed after an examination request according [chapter 6.6 patent gazette]|

---

2019-11-19| B06U| Preliminary requirement: requests with searches performed by other patent offices: procedure suspended [chapter 6.21 patent gazette]|

---

2020-08-25| B09A| Decision: intention to grant [chapter 9.1 patent gazette]|

---

2020-10-20| B16A| Patent or certificate of addition of invention granted [chapter 16.1 patent gazette]|Free format text: PRAZO DE VALIDADE: 20 (VINTE) ANOS CONTADOS A PARTIR DE 04/04/2013, OBSERVADAS AS CONDICOES LEGAIS. |

优先权:

---

申请号 | 申请日 | 专利标题

---

US13/446,850|2012-04-13|

---

US13/446,850|US9020652B2|2012-04-13|2012-04-13|Event processing system for an electrical power system|

---